> * Change NUMERIC to enforce the maximum precision, and increase it

> * Change NUMERIC data type to use base 10,000 internally

on the namespace not the name; pg_ is not a reserved prefix for table
names anymore.  From Fernando Nasser.

pg_dumpall.

2) Suppress some error logs for the request to other drivers.

names are handled OK.

entries, per pghackers discussion.  This fixes aggregates to live in
namespaces, and also simplifies/speeds up lookup in parse_func.c.
Also, add a 'proimplicit' flag to pg_proc that controls whether a type
coercion function may be invoked implicitly, or only explicitly.  The
current settings of these flags are more permissive than I would like,
but we will need to debate and refine the behavior; for now, I avoided
breaking regression tests as much as I could.

single-user escape path always works.

Properly warn of invalid pg_dumpall options;  minor quoting cleanups.

and --without-zlib to turn them off.

SELECT schema1.func2(...).  Aggregate names can be qualified at the
syntactic level, but the qualification is ignored for the moment.

>         o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW

< * -Add domain capability [domain] (Rod Taylor)
> * -Add domain capability (Rod Taylor)

> * Add Intimate Shared Memory(ISM) for Solaris
> * Add documentation to lock shared memory into RAM for each OS, if possible

> 	o Fix PL/pgSQL RENAME to work on on variable names

refcursors.

Some other minor wording improvements.

timestamp.

This is necessary for mulibyte character sequences.
See "[HACKERS] PQescapeBytea is not multibyte aware" thread posted around
2002/04/05 for more details.

> * Abort SET changes made in aborted transactions