was mentioned on the man page for the underlying CREATE USER command,
but it should be explained here too.

This restores the Linux behavior to what it was in PG 7.0 and 7.1, and
causes other platforms to agree.  (Other well-tested platforms like HPUX
were doing it this way already.)  Per pghackers discussion over the past
month or so.

(backslash-r, backslash-n) for protection against newline-conversion
munging.  In future we will also tweak COPY FROM, but this part of the
change should be backwards-compatible.  Per pghackers discussion.
Also, update COPY reference page to describe the backslash conversions
more completely and accurately.

of pointers is required.  Patch from Teodor Sigaev per pghackers
discussion.  It's an ugly kluge but avoids forcing initdb; we'll put
a better fix into 7.3 or later.

inner indexscan (ie, one with runtime keys).  ExecIndexReScan must
compute or recompute runtime keys even if we are rescanning in the
EPQ case.  TidScan seems to have comparable problems.  Per bug
noted by Barry Lind 11-Feb-02.

< 	o prevent lose of indexes, permissions, inheritance (Bruce)
---
> 	o prevent loss of indexes, permissions, inheritance (Bruce)

the CREATE DATABASE command right in pg_dump -C case.

into a virgin database, ie, one created from template0, if there are any
site-local additions in template1.

crash on Solaris when over disk quota.  Instead, report such failures
via elog(DEBUG).

< * Have checkpoint process identify itself via ps status display

> * Have checkpoint process identify itself via ps status display

Patch from sugita@sra.co.jp.

Teodor Sigaev <teodor@stack.net>.

< * Allow row re-use with automatic vacuum (Tom)
356c355
<
---
> * Provide automatic scheduling of background vacuum (Tom)

< * Allow row re-use without vacuum (Tom)
---
> * Allow row re-use with automatic vacuum (Tom)

> * Flush cached query plans when their underlying catalog data changes

bug.template.

This fixes references to 7.1.3 (I think).  It also
modifies the japanese
FAQ, so I'm not sure if that's done correctly.

Chris

please apply.

Andreas

> * Prevent SIGHUP and 'pg_ctl reload' from changing command line
>   specified parameters to postgresql.conf defaults