diff options
| author | Tom Lane | 2012-05-11 21:46:08 +0000 |
|---|---|---|
| committer | Tom Lane | 2012-05-11 21:46:37 +0000 |
| commit | d0c231d13224621c2bd1e7e0466dd8000bdc1a02 (patch) | |
| tree | 16f97dffc2500f0fb8ff435ce44a7b2924068025 /src/backend/postmaster/bgwriter.c | |
| parent | 2cfb1c6f77734db81b6e74bcae630f93b94f69be (diff) | |
Cosmetic adjustments for postmaster's handling of checkpointer.
Correct some comments, order some operations a bit more consistently.
No functional changes.
Diffstat (limited to 'src/backend/postmaster/bgwriter.c')
| -rw-r--r-- | src/backend/postmaster/bgwriter.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/postmaster/bgwriter.c b/src/backend/postmaster/bgwriter.c index 5daf8c6177b..9ad7178aeb8 100644 --- a/src/backend/postmaster/bgwriter.c +++ b/src/backend/postmaster/bgwriter.c @@ -15,9 +15,9 @@ * The bgwriter is started by the postmaster as soon as the startup subprocess * finishes, or as soon as recovery begins if we are doing archive recovery. * It remains alive until the postmaster commands it to terminate. - * Normal termination is by SIGUSR2, which instructs the bgwriter to exit(0). - * Emergency termination is by SIGQUIT; like any - * backend, the bgwriter will simply abort and exit on SIGQUIT. + * Normal termination is by SIGTERM, which instructs the bgwriter to exit(0). + * Emergency termination is by SIGQUIT; like any backend, the bgwriter will + * simply abort and exit on SIGQUIT. * * If the bgwriter exits unexpectedly, the postmaster treats that the same * as a backend crash: shared memory may be corrupted, so remaining backends |