pgsql: Adjust comment in .history file to match recovery target - Mailing list pgsql-committers

From sriggs@postgresql.org (Simon Riggs)
Subject pgsql: Adjust comment in .history file to match recovery target
Date
Msg-id 20100319110515.26B157541D0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Adjust comment in .history file to match recovery target specified. Comment
present since 8.0 was never fully meaningful, since two recovery targets
cannot be specified. Refactor recovery target type to make this change
and associated code easier to understand. No change in function.

Bug report arising from internal support question.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.382 -> r1.383)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.382&r2=1.383)
    pgsql/src/include/access:
        xlog.h (r1.103 -> r1.104)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/xlog.h?r1=1.103&r2=1.104)

pgsql-committers by date:

Previous
From: sriggs@postgresql.org (Simon Riggs)
Date:
Subject: pgsql: Reset btpo.xact following recovery of btree delete page.
Next
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Prevent the injection of invalidly encoded strings by PL/Python