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

to pghackers.  Use this to do searching for ambiguous functions ---
it will get more uses soon.

Jun Kuwamura

> > on postgres on Unixware with GCC built with gnu-as and gnu-ld.

Remove leading spaces in conditional tests in patch and Makefile.aix.

Nicolas Bazin

the decision not to make renamerel() update the sequence name that
is stored within sequences themselves (thanks to Tom Lane), and adds
some rudimentary regression tests for ALTER TABLE ... RENAME on
non-table relations.

Neil Conway

> 	o -Allow INSERT INTO my_table VALUES (a, b, c, DEFAULT, x, y, z, ...)

Rod Taylor

insert on a view), and noticed that psql wouldn't show the list of rules
set up on a view, like it does for tables.

The fix was extremely simple, so I figured I'd share it.  Not sure what
the standard is for communicating these things, so I've attached the diff
file for /src/bin/psql/describe.c.

Paul (?)

Rod Taylor

file, which is not the actual end of the file. One side effect of that
is that if you are i n a ifdef block, you get a wrong error telling you
that a endif is missing.

This patch corrects pgc.l and also adds a test of this problem to
test1.pgc. To  convince you apply the patch to test1.pgc first then try
to compile the test the n apply the patch to pgc.l.

The patch moves the test of the scope of an ifdef block to the end of
the file b eeing parsed, including all includes files, ... .

Nicolas Bazin

The patch enables the mips2 ISA for the ll/sc operations, and then restores
it when done.  The kernel/libc emulation code will take over on CPUs without
ll/sc, and on CPUs with it, it'll use the operations provided by the CPU.

Combined with the earlier fix (removing -mips2), postgresql builds again on
mips and mipsel.  The patch is against 7.2-7.

Oliver Elphick

INSERT statements to the planner.  Taking it out of the parser was right
(so that defaults don't get into stored rules), but it has to happen
before rewrite rule expansion, else references to NEW.field behave
incorrectly.  Accordingly, add a step to the rewriter to insert defaults
just before rewrite-rule expansion.

> * -Add new pg_proc cachable settings to specify whether function can be

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).