pgsql: Rename PM_RECOVERY_CONSISTENT and PMSIGNAL_RECOVERY_CONSISTENT. - Mailing list pgsql-committers

From rhaas@postgresql.org (Robert Haas)
Subject pgsql: Rename PM_RECOVERY_CONSISTENT and PMSIGNAL_RECOVERY_CONSISTENT.
Date
Msg-id 20100515200132.DD3607541D2@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Rename PM_RECOVERY_CONSISTENT and PMSIGNAL_RECOVERY_CONSISTENT.

The new names PM_HOT_STANDBY and PMSIGNAL_BEGIN_HOT_STANDBY more accurately
reflect their actual function.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.412 -> r1.413)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.412&r2=1.413)
    pgsql/src/backend/postmaster:
        postmaster.c (r1.607 -> r1.608)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.607&r2=1.608)
    pgsql/src/include/storage:
        pmsignal.h (r1.30 -> r1.31)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/pmsignal.h?r1=1.30&r2=1.31)

pgsql-committers by date:

Previous
From: andrewd@pgfoundry.org (User Andrewd)
Date:
Subject: pgbuildfarm - client-code: New Directory
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Ensure that pg_restore -l will output DATABASE entries whether or