information.

right in the failure.  We can always re-add it if required.

but the documentation still said so.

Kris Jurka

with Postgres.

clamp the estimated number of groups to table row count over 10, instead
of table row count; this reflects a heuristic that people probably won't
group over a near-unique set of columns, and the knowledge that we don't
currently have any way to estimate the correlation of the columns better
than guessing.  This change creates a trivial plan change in one of the
regression tests.

look at the actual aggregate transition datatypes and the actual overhead
needed by nodeAgg.c, instead of using pessimistic round numbers.
Per a discussion with Michael Tiemann.

defining List.

Solaris and should be a little faster anyway, since in most scenarios
all but perhaps the last path component will already exist.

functions of the aggregate, at both aggregate creation and execution times.

utils/cache/lsyscache.c where it can be used by other things.  Also
cleans up both get_usesysid() and get_grosysid() a bit. From Stephen
Frost.

Relation. Patch from Alvaro Herrera, minor editorializing by
Neil Conway.

stand to be rewritten altogether, but for now just stick a finger in
the dike.

does not match what the query expected. From Brendan Jurd, minor
editorializing by Neil Conway.

command.  This is useful because we can allow truncation of tables
referenced by foreign keys, so long as the referencing table is
truncated in the same command.

Alvaro Herrera

Tom.

to avoid problems when a cursor depends on objects created or changed in
the same subtransaction.  We'd like to do better someday, but this seems
the only workable answer for 8.0.1.

for the postmaster to start.  Dave Page

it agrees with the default value of max_stack_depth.

column values in -d mode.  Per report from Marty Scholes.  This doesn't
completely solve the issue, because we still need multiple copies of the
field value, but at least one copy can be got rid of painlessly ...