mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

We now accept read-only connections in state PM_RECOVERY_CONSISTENT.

Browse Source
This commit is contained in:
Robert Haas 2010-05-14 18:08:33 +00:00
parent 0b38f3b192
commit a724584735
1 changed files with 7 additions and 9 deletions

16
src/backend/postmaster/postmaster.c

@ -37,7 +37,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/postmaster/postmaster.c,v 1.606 2010/04/28 16:10:42 heikki Exp $ * $PostgreSQL: pgsql/src/backend/postmaster/postmaster.c,v 1.607 2010/05/14 18:08:33 rhaas Exp $
* *
* NOTES * NOTES
* *
@ -238,14 +238,12 @@ static bool RecoveryError = false; /* T if WAL recovery failed */
* *
* When the startup process is ready to start archive recovery, it signals the * When the startup process is ready to start archive recovery, it signals the
* postmaster, and we switch to PM_RECOVERY state. The background writer is * postmaster, and we switch to PM_RECOVERY state. The background writer is
* launched, while the startup process continues applying WAL. * launched, while the startup process continues applying WAL. If Hot Standby
* After reaching a consistent point in WAL redo, startup process signals * is enabled, then, after reaching a consistent point in WAL redo, startup
* us again, and we switch to PM_RECOVERY_CONSISTENT state. There's currently * process signals us again, and we switch to PM_RECOVERY_CONSISTENT state and
* no difference between PM_RECOVERY and PM_RECOVERY_CONSISTENT, but we * begin accepting connections to perform read-only queries. When archive
* could start accepting connections to perform read-only queries at this * recovery is finished, the startup process exits with exit code 0 and we
* point, if we had the infrastructure to do that. * switch to PM_RUN state.
* When archive recovery is finished, the startup process exits with exit
* code 0 and we switch to PM_RUN state.
* *
* Normal child backends can only be launched when we are in PM_RUN or * Normal child backends can only be launched when we are in PM_RUN or
* PM_RECOVERY_CONSISTENT state. (We also allow launch of normal * PM_RECOVERY_CONSISTENT state. (We also allow launch of normal