no bug related to this functionality in HEAD, but it's worth adding a test
for anyway.) From Andrew Dunstan.

want to handle set inputs, it should just pass NULL for isDone, not make
its own failure check.

the "extern" keyword from function definitions, reorganize some
PG_GETARG_XXX() usage, and similar.

other PLs besides plpgsql.  Andrew Dunstan

of database name before table name
when VACUUMing or ANALYZing a table.

Cosimo Streppone

AtCommit_Portals is restarted when a portal is deleted. This is
necessary since the deletion of a portal may cause the deletion of
another which on rare occations may cause the iterator to return a
deleted portal an thus a renewed attempt delete.

Thomas Hallgren

instead of pg_usleep.

Backpatch to 8.0.X.

Robert Treat

Update Chinese FAQ for HTML.

methods: they all invoke UpdateStats() since they have computed the
number of heap tuples, so I created a function in catalog/index.c that
each AM now calls.

laser@pgsqldb.com

collector messages, per recent discussion on pgsql-patches. This
actually required quite a few changes -- for example,
"databaseid != InvalidOid" was used to check whether a slot in the
backend entry table was initialized, but that no longer works since
the slot might be initialized prior to receiving the BESTART message
which contains the database id. We now use procpid > 0 to indicate
that a slot is non-empty.

Other changes:

- various comment improvements and cleanups
- there's no need to zero-out the entire activity buffer in
  pgstat_add_backend(), we can just set activity[0] to '\0'.
- remove the counting of the # of connections to a database; this
  was not used anywhere

One change in behavior I wasn't sure about: previously, the code
would create a hash table entry for a database as soon as any message
was received whose header referenced that database. Now, we only
create hash table entries as needed (so for example BESTART won't
create a database hash table entry, since it doesn't need to
access anything in the per-db hash table). It would be easy enough
to retain the old behavior, but AFAICS it is not required.

memset() or MemSet() to a char *. For one, memset()'s first argument is
a void *, and further void * can be implicitly coerced to/from any other
pointer type.

Heikki Linnakangas

< * -Check for unreferenced table files created by transactions that were
> * Check for unreferenced table files created by transactions that were

WITHOUT CLUSTER for cluster failure of a single table in a full db
cluster.

> * Fix sgmltools so PDFs can be generated with bookmarks

> * Allow postgresql.conf values to be set so they can not be changed by
>   the user

< * Add session start time and last statement time to pg_stat_activity
> * -Add session start time and last statement time to pg_stat_activity
134c134
< * Add the client IP address and port to pg_stat_activity
> * -Add the client IP address and port to pg_stat_activity

a few sections up.

checkin. My apologies for breaking the tests.

actually follow the protocol; per example from Kris Jurka.

* Add session start time to pg_stat_activity
* Add the client IP address and port to pg_stat_activity

Original patch from Magnus Hagander, code review by Neil Conway. Catalog
version bumped. This patch sends the client IP address and port number in
every statistics message; that's not ideal, but will be fixed up shortly.

need to be created by hand anymore.

Christopher Browne

Vladimir Chukharev

and VACUUM: in the interval between adding a new page to the relation
and formatting it, it was possible for VACUUM to come along and decide
it should format the page too.  Though not harmful in itself, this would
cause data loss if a third transaction were able to insert tuples into
the vacuumed page before the original extender got control back.