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

Поиск
Список
Период
Сортировка
От heikki@postgresql.org (Heikki Linnakangas)
Тема pgsql: Fix bug in %r handling in recovery_end_command, it always came
Дата
Msg-id 20100318091855.099D97541D0@cvs.postgresql.org
обсуждение исходный текст
Список 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)

В списке pgsql-committers по дате отправления:

Предыдущее
От: heikki@postgresql.org (Heikki Linnakangas)
Дата:
Сообщение: pgsql: Add restartpoint_command option to recovery.conf.
Следующее
От: petere@postgresql.org (Peter Eisentraut)
Дата:
Сообщение: pgsql: Use data-type specific conversion functions also in plpy.execute