> 	  without using PL/PgSQL EXECUTE, needs cached plan invalidation

- Fixed one bug in structure handling resulting in using sizeof indicator instead of variable.

some old code to add PK constraints to CREATE TABLE. That stuff
had been removed as part of my original patch for pg_dump a
little while ago.

The attached patch fixes this by removing (again :-) ) the
code in dumpTables() to perform PK creation during CREATE
TABLE. I briefly tested it locally and it fixes both of
Tom's test cases.

Please apply.

Cheers,

Neil

--
Neil Conway <neilconway@rogers.com>

for Solaris on SPARC.  Scott Brunza (sbrunza@sonalysts.com) gets
credit for identifying the issue, making the change, and doing
the regression tests.

Earlier testing on 7.2rc2 and 7.2 showed performance gains of
1% to 10% on pgbench, osdb-pg, and some locally developed apps.

Solaris Intimate Shared Memory is described in "SOLARIS INTERNALS
Core Kernel Components" by Jim Mauro and Richard McDougall,
Copyright 2001 Sun Microsystem, Inc.  ISBN 0-13-022496-0

P.J. "Josh" Rovero

the libpgtcl "pg_execute" command. This was mentioned on
pgsql-interfaces on Mar 3. I am posting it here in the hope that someone
will check to see if it makes sense and is correct SGML-wise.  I did run
it through jade, but this is my first try at this sort of thing.

ljb

> * 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