[COMMITTERS] pgsql: Remove piece of code to zero out minRecoveryPoint when starting

2010-02-08 Thread Heikki Linnakangas
Log Message: --- Remove piece of code to zero out minRecoveryPoint when starting crash recovery. It's zeroed out whenever a checkpoint is written, so the only scenario where the removed code did anything is when you kill archive recovery, remove recovery.conf, and start up the server, so th

[COMMITTERS] pgsql: Update high availability/replication documentation chart for new

2010-02-08 Thread Bruce Momjian
Log Message: --- Update high availability/replication documentation chart for new hot standby featureset. Modified Files: -- pgsql/doc/src/sgml: high-availability.sgml (r1.38 -> r1.39) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/high-availa

[COMMITTERS] pgsql: Add C comments that HEAP_MOVED_* define usage is only for pre-9.0

2010-02-08 Thread Bruce Momjian
Log Message: --- Add C comments that HEAP_MOVED_* define usage is only for pre-9.0 binary upgrades. Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.116 -> r1.117) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c?r1

Re: [COMMITTERS] pgsql: Add C comments that HEAP_MOVED_* define usage is only for pre-9.0

2010-02-08 Thread Tom Lane
[email protected] (Bruce Momjian) writes: > Log Message: > --- > Add C comments that HEAP_MOVED_* define usage is only for pre-9.0 binary > upgrades. This seems fairly redundant with the comments that were already there. regards, tom lane -- Sent via pgsql-c

Re: [COMMITTERS] pgsql: Add C comments that HEAP_MOVED_* define usage is only for pre-9.0

2010-02-08 Thread Bruce Momjian
Tom Lane wrote: > [email protected] (Bruce Momjian) writes: > > Log Message: > > --- > > Add C comments that HEAP_MOVED_* define usage is only for pre-9.0 binary > > upgrades. > > This seems fairly redundant with the comments that were already there. The comment was at the top of Set

[COMMITTERS] pgsql: Fix serious performance bug in new implementation of VACUUM FULL:

2010-02-08 Thread Tom Lane
Log Message: --- Fix serious performance bug in new implementation of VACUUM FULL: cluster_rel necessarily builds an all-new toast table, so it's useless to then go and VACUUM FULL the toast table. Modified Files: -- pgsql/src/backend/commands: vacuum.c (r1.405 -> r

Re: [COMMITTERS] pgsql: Add C comments that HEAP_MOVED_* define usage is only for pre-9.0

2010-02-08 Thread Bruce Momjian
bruce wrote: > Tom Lane wrote: > > [email protected] (Bruce Momjian) writes: > > > Log Message: > > > --- > > > Add C comments that HEAP_MOVED_* define usage is only for pre-9.0 binary > > > upgrades. > > > > This seems fairly redundant with the comments that were already there. > >

[COMMITTERS] pgsql: Remove obsolete comment about 'fsm' argument, which isn't an

2010-02-08 Thread Heikki Linnakangas
Log Message: --- Remove obsolete comment about 'fsm' argument, which isn't an argument anymore. Modified Files: -- pgsql/src/backend/catalog: storage.c (r1.8 -> r1.9) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/storage.c?r1=1.8&r2=1.

[COMMITTERS] pgsql: Remove obsolete comment about 'fsm' argument, which isn't an

2010-02-08 Thread Heikki Linnakangas
Log Message: --- Remove obsolete comment about 'fsm' argument, which isn't an argument anymore. Tags: REL8_4_STABLE Modified Files: -- pgsql/src/backend/catalog: storage.c (r1.6 -> r1.6.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/

[COMMITTERS] pgsql: Create an official API function for C functions to use to check

2010-02-08 Thread Tom Lane
Log Message: --- Create an official API function for C functions to use to check if they are being called as aggregates, and to get the aggregate transition state memory context if needed. Use it instead of poking directly into AggState and WindowAggState in places that shouldn't know so m

[COMMITTERS] pgsql: Rearrange lazy-vacuum code a little bit to reduce the window

2010-02-08 Thread Tom Lane
Log Message: --- Rearrange lazy-vacuum code a little bit to reduce the window between truncating the table and transaction commit. This isn't really making it safe, but at least there is no good reason to do free space map cleanup within the risk window. Don't lock out cancel interrupts u

[COMMITTERS] pgsql: Allow free space map vacuuming to be interrupted.

2010-02-08 Thread Tom Lane
Log Message: --- Allow free space map vacuuming to be interrupted. Modified Files: -- pgsql/src/backend/storage/freespace: freespace.c (r1.74 -> r1.75) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/freespace/freespace.c?r1=1.74&r2=1.75