I took the opportunity to remove the pg_proc.proistrusted field.

GUC support.  It's now possible to set datestyle, timezone, and
client_encoding from postgresql.conf and per-database or per-user
settings.  Also, implement rollback of SET commands that occur in a
transaction that later fails.  Create a SET LOCAL var = value syntax
that sets the variable only for the duration of the current transaction.
All per previous discussions in pghackers.

DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause,
similar to TRIGGER syntaxes.  To allow loading of existing pg_dump
files containing COMMENT ON RULE, the COMMENT code will still accept
the old syntax --- but only if the target rulename is unique across
the whole database.

and --without-zlib to turn them off.

volatile), rather than the old cachable/noncachable distinction.  This
allows indexscan optimizations in many places where we formerly didn't.
Also, add a pronamespace column to pg_proc (it doesn't do anything yet,
however).

and/or with GUC variables.

 Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)

 Allow CREATE TABLE AS ... SELECT in PL/PgSQL (Tom)

Also, fix debug logging of parse/plan trees so that the messages actually
go through elog(), not directly to stdout.

> > to perform sql command:
> >  update pg_amop set amopreqcheck = true where amopclaid =
> >       (select oid from pg_opclass where opcname = 'gist_txtidx_ops');
>
> Oleg, sorry, I don't understand where this should appear.  In the README
> file, and if so, where?  Is this something only for people upgrading
> from 7.2?

Sorry Bruce, I was unclear. I have attached patch to Readme.tsearch
Also, It'd be worth to mention in Changes to point users of tsearch
about importang upgrade notices.

Oleg Bartunov

	Ensure that sequence counters do not go backwards after a crash

variables.  New commands ALTER DATABASE ... SET and ALTER USER ... SET.

on behalf of unprivileged users.  Also, make '=' optional in CREATE
DATABASE syntax.  From Gavin Sherry, with kibitzing and docs by Tom Lane.

And listing QNX 6 as both supported and unsupported is probably not helpful.

now generated from DocBook sources.

Purge "Postgres" in favor of "PostgreSQL" in docs. ref/ not yet done.