pgsql: Avoid starting walreceiver in states where it shouldn't be - Mailing list pgsql-committers

From rhaas@postgresql.org (Robert Haas)
Subject pgsql: Avoid starting walreceiver in states where it shouldn't be
Date
Msg-id 20100527020138.0A53A7541D2@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Avoid starting walreceiver in states where it shouldn't be running.

In particular, it's bad to start walreceiver when in state
PM_WAIT_BACKENDS, because we have no provision to kill walreceiver
when in that state.

Fujii Masao

Modified Files:
--------------
    pgsql/src/backend/postmaster:
        postmaster.c (r1.609 -> r1.610)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.609&r2=1.610)

pgsql-committers by date:

Previous
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Adjust comment to reflect that we now have Hot Standby.
Next
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Make it more clear that you need to release savepoint with