< * Delay fsync() when other backends are about to commit too [fsync]
> * Delay fsync() when other backends are about to commit too

< * Add MATCH PARTIAL referential integrity [foreign]
> * Add MATCH PARTIAL referential integrity

> * Allow cross-db queries with transaction sematics

< * Allow queries across multiple databases [crossdb]

On Mon, 2004-01-26 at 21:28, Peter Eisentraut wrote:
> Christophe Combelles wrote:
> > At the bottom of this doc file :
> > file:///usr/share/doc/postgresql-doc/html/tutorial-createdb.html
> > "and it also happens that that user always has permission"
> >                       ---- x2
> The first "that" serves as a conjuction, the second one serves as an
> article.  Looks correct to me.

A better workaround for the sentence would be something like:

        "and it also happens that the user always has permission"

Looks easier to read, I think.

Enver ALTIN (a.k.a. skyblue)

<
> * Allow substring/replace() to get/set bit values

< 	o Allow Java server-side programming, http://pljava.sourceforge.net
< 	  [java]
> 	o Allow Java server-side programming [java]

> 	o Disallow dropping of an inherited constraint

< * Make blind writes go through the file descriptor cache

< * Point-in-time data recovery using backup and write-ahead log
< * Create native Win32 port, http://momjian.postgresql.org/main/writings/pgsql/win32.html
> * Point-in-time data recovery using backup and write-ahead log,
>   http://momjian.postgresql.org/main/writings/pgsql/project/pitr.html
> * Create native Win32 port, http://momjian.postgresql.org/main/writings/pgsql/project/win32.html

Make btree index creation and initial validation of foreign-key constraints
use maintenance_work_mem rather than work_mem as their memory limit.
Add some code to guc.c to allow these variables to be referenced by their
old names in SHOW and SET commands, for backwards compatibility.

> * Make pg_restore continue after errors, so it acts more like pg_dump scripts

some time ago and recent patch from Gavin Sherry.  Update documentation
to point out that trailing spaces are insignificant in char(n).

<
> * Allow libpq to return information about prepared queries

Tom Lane for some editorial suggestions.

> * -Add checks for fclose() failure (Tom)

> * -Add checks for fclose() failure (Tom)

to handle memory management for char pointers returned by libpq functions.
Original patch by Gavin Sherry, some tweaking and consistency improvements
by Neil Conway.

> * Dump large object comments in custom dump format

Sherry, editorializing by Neil Conway.

> * Joe is Joe Conway <mail@joeconway.com>

and PL/pgSQL only prints queries on first function call.

per Dennis Bjorklund.  I did not force initdb for this, but
you'd need to do one to get the improved view.

that it's good to join where there are join clauses rather than where there
are not.  Also enable it to generate bushy plans at need, so that it doesn't
fail in the presence of multiple IN clauses containing sub-joins.  These
changes appear to improve the behavior enough that we can substantially reduce
the default pool size and generations count, thereby decreasing the runtime,
and yet get as good or better plans as we were getting in 7.4.  Consequently,
adjust the default GEQO parameters.  I also modified the way geqo_effort is
used so that it affects both population size and number of generations;
it's now useful as a single control to adjust the GEQO runtime-vs-plan-quality
tradeoff.  Bump geqo_threshold to 12, since even with these changes GEQO
seems to be slower than the regular planner at 11 relations.

> * Improve CREATE SCHEMA regression test