diff options
| author | Heikki Linnakangas | 2009-02-23 07:58:14 +0000 |
|---|---|---|
| committer | Heikki Linnakangas | 2009-02-23 07:58:14 +0000 |
| commit | a57bf5ec06376803c8ed2af36afd461704abcfc1 (patch) | |
| tree | 2942dcaa5c8474201aa886e7a5aef1dd3c291388 | |
| parent | 30f96acd1a4ca704100c7b836a58e9ef3dc17b95 (diff) | |
comment fixes.
| -rw-r--r-- | src/backend/postmaster/postmaster.c | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index ed921e7cc1..0a06632922 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -244,13 +244,10 @@ static bool RecoveryError = false; /* T if recovery failed */ * could start accepting connections to perform read-only queries at this * point, if we had the infrastructure to do that. * - * When the WAL redo is finished, the startup process signals us the third - * time, and exits. We don't process the 3d signal immediately but when we - * see the that the startup process has exited, we check that we have - * received the signal. If everything is OK, we then switch to PM_RUN state. - * The startup process can also skip the recovery and consistent recovery - * phases altogether, as it will during normal startup when there's no - * recovery to be done, for example. + * When the WAL redo is finished, the startup process exits with exit code 0 + * and we switch to PM_RUN state. The startup process can also skip the + * recovery and consistent recovery phases altogether, as it will during + * normal startup when there's no recovery to be done, for example. * * Normal child backends can only be launched when we are in PM_RUN state. * (We also allow it in PM_WAIT_BACKUP state, but only for superusers.) |