Change the signaling between startup process and postmaster. Startup process
authorHeikki Linnakangas <heikki@enterprisedb.com>
Fri, 30 Jan 2009 14:24:55 +0000 (16:24 +0200)
committerHeikki Linnakangas <heikki@enterprisedb.com>
Fri, 30 Jan 2009 14:24:55 +0000 (16:24 +0200)
commit22f88933dd3a4533f512991dabb1f8d895f93bd6
tree32da2697d2aa7f10f8bac98c70ccc2e17a91654b
parentd464d8e87c7bea818abbc68b83886105f2171e65
Change the signaling between startup process and post Startup process
now tells postmaster about the start, consistent point, and completion of
WAL redo, using signals. It now returns with exit code 0 when WAL replay is
aborted with SIGTERM. Background writer is launched as soon as we start WAL
redo, so that it can perform restartpoints before reaching consistent state.
Postmaster handles unexpected death of the startup process gracefully. In
case of a fast shutdown, bgwriter performs a "shutdown restartpoint", similar
to a shutdown checkpoint.
src/backend/access/transam/xlog.c
src/backend/bootstrap/bootstrap.c
src/backend/postmaster/bgwriter.c
src/backend/postmaster/postmaster.c
src/include/access/xlog.h
src/include/storage/pmsignal.h