pgsql: Fix bug in %r handling in recovery_end_command, it always came

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix bug in %r handling in recovery_end_command, it always came
Date: 2010-03-18 09:18:55
Message-ID: 20100318091855.099D97541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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. That didn't matter before, but in 8.4 bgwriter is active during
recovery and can modify the control file concurrently.

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
pgsql/src/backend/access/transam:
xlog.c (r1.345.2.7 -> r1.345.2.8)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.345.2.7&r2=1.345.2.8)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2010-03-18 13:23:57 pgsql: Use data-type specific conversion functions also in plpy.execute
Previous Message Heikki Linnakangas 2010-03-18 09:17:18 pgsql: Add restartpoint_command option to recovery.conf.