> * Have VACUUM FULL use REINDEX rather than index vacuum

About section 8.5.1.5. ("Special Values"):

I suggest adding LOCALTIMESTAMP and LOCALTIME to the first paragraph.
Maybe it should be phrased as:

  The following SQL-compatible functions can be used to obtain
  current datetime-related values: CURRENT_DATE, CURRENT_TIME,
  CURRENT_TIMESTAMP, LOCALTIME and LOCALTIMESTAMP.
  (See Section 9.8.4.)

Troels Arvin

misscanning of this construct:

SELECT ''hello world''
-- SELECT ''goodbye world''
::text;

with a little dirty snprintf() usage which I used some years ago:

    snprintf(path, BUFSIZ, "%s/lo_dump.index", path);

Karel Zak

> * COMMENT ON [ CAST | CONVERSION | OPERATOR CLASS | LARGE OBJECT | LANGUAGE ]
>   (Christopher)

than having CFLAGS= in the template files.

It uses -O2 for gcc (generated by autoconf), and -O for non-gcc, unless
the template overrides it.

> * COMMENT ON [ CAST | CONVERSION | OPERATOR CLASS | LARGE OBJECT ] (Christopher)

Have log_duration print when log_min_duration_statement prints.

function to prevent multiple threads using automatic cursors on
the same connection from stomping over each others cursor.

Jan

<
346a346
> * Remove CREATE CONSTRAINT TRIGGER

< 	o Sample implementation in contrib/rserv
29c28,29
< * Create native Win32 port [win32]
> * Create native Win32 port, http://momjian.postgresql.org/main/writings/pgsql/win32.html
>
367c367,368
< * Two-phase commit to implement distributed transactions
> * Add two-phase commit to all distributed transactions with
>   offline/readonly server status or administrator notification for failure

> * Use background process to write dirty shared buffers to disk

only read this because of Niel :-)

Robert Treat

Fix pg_restore tar log output bug where Special flag wasn't being
initialized; bug seen on XP.

Change log line to be "duration:  ms  query:"

Indent multi-line queries with a tab in the server logs.

one side of a binary operator is probably supposed to be the same type
as the other operand' will be applied for domain types.  This worked
in 7.3 but was broken in 7.4 due to code rearrangements.  Mea culpa.

a single LEFT JOIN query instead of firing the check trigger for each
row individually.  Stephan Szabo, with some kibitzing from Tom Lane and
Jan Wieck.

- Fixed typo in ecpg for Informix dec_t type.
- Fixed precision handling in Informix compat funxtions.

before it is de-backslashed, not after.  This allows the null string \N
to be reliably distinguished from the data value \N (which must be
represented as \\N).  Per bug report from Manfred Koizar ... but it's
amazing this hasn't been reported before ...
Also, be consistent about encoding conversion for null string: the form
specified in the command is in the server encoding, but what is sent
to/from client must be in client encoding.  This never worked quite
right before either.