Skip site navigation (1) Skip section navigation (2)

pgsql: Add restartpoint_command option to recovery.conf.

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add restartpoint_command option to recovery.conf.
Date: 2010-03-18 09:17:18
Message-ID: 20100318091718.BC14D7541D0@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Add restartpoint_command option to recovery.conf. Fix bug in %r handling
in recovery_end_command, it always came out as 0 because InRedo was
cleared before recovery_end_command was executed. Also, always take
ControlFileLock when reading checkpoint location for %r.

The recovery_end_command bug and the missing locking was present in 8.4
as well, that part of this patch will be backported separately.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        recovery-config.sgml (r2.2 -> r2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/recovery-config.sgml?r1=2.2&r2=2.3)
    pgsql/src/backend/access/transam:
        xlog.c (r1.381 -> r1.382)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.381&r2=1.382)

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2010-03-18 09:18:55
Subject: pgsql: Fix bug in %r handling in recovery_end_command, it always came
Previous:From: Simon RiggsDate: 2010-03-18 07:01:05
Subject: pgsql: Add vacuum_defer_cleanup_age to postgresql.conf.sample.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group