Bring python up to date ...

From: D'Arcy J.M. Cain <darcy@druid.net>

will pass through rather than spitting up.  This is necessary to handle
cases where coerce_type causes a subexpression to be retransformed, as in
	SELECT count(*) + 1.0 FROM table

remove optimizer's arbitrary limit on how large a join it will use hashing
for.  (The limit was too large to prevent the problems we'd been seeing,
anyway...)

fixed-size hashtable.  This should prevent 'hashtable out of memory' errors,
unless you really do run out of memory.  Note: target size for hashtable
is now taken from -S postmaster switch, not -B, since it is local memory
in the backend rather than shared memory.

ALTER TABLE RENAME with extents.
Ole Gjerde

Jan

looks
like someone just didn't add support for multiple segments for
truncation.

The following patch seems to do the right thing, for me at least.
It passed my tests, my data looks right(no data that shouldn't be in
there) and regression is ok.

Ole Gjerde

Update pointers to where the register/mailing list pages are found on the
wweb site ..

for SERIAL column's constraint, but forgot to increase space palloc'd...

Apply freebsd specific patches dealign with ELF system from FreeBSD's
ports collection ...

for GEQO ...

is evaluated.  This bounds memory usage to something reasonable even
when many tables are being joined.

reasonable plans again.  Still eats memory like there's no tomorrow,
however :-(.

lost most of target list and thus 'make clean' didn't clean up very well.

for compatibility with older C++ libraries.

segments, and my indexes had 3(Yes, it DOES work!).
DROP TABLE removed ALL segments from the table, but only the main index
segment.

So it looks like removing the table itself is using mdunlink in md.c,
while removing indexes uses FileNameUnlink() which only unlinks 1 file.
As far as I can tell, calling FileNameUnlink() and mdunlink() is basically
the same, except mdunlink() deletes any extra segments.

I've done some testing and it seems to work.  It also passes regression
tests(except float8, geometry and rules, but that's normal).

If this patch is right, this fixes all known multi-segment problems on
Linux.

Ole Gjerde

configtype.patch simply fixes a typo in config.h.in
pg_dump.c.patch Updates a bunch of error messages to include a reason
from
                the backend, and also removes a couple of unnecessary
if's

Ole Gjerde