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

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

From

heikki@postgresql.org (Heikki Linnakangas)

Date:

18 March 2010, 09:19:12

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)