mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-27 08:57:19 +02:00
24ecde7742
On MacOS X, and apparently also on other BSD-derived systems, attaching a debugger causes getppid() to return the pid of the debugging process rather than the actual parent PID. As a result, debugging the autovacuum launcher, startup process, or WAL sender on such systems causes it to exit, because the previous coding of PostmasterIsAlive() detects postmaster death by testing whether getppid() == PostmasterPid. Work around that behavior by checking the return value of getppid() more carefully. If it's PostmasterPid, the postmaster must be alive; if it's 1, assume the postmaster is dead. If it's any other value, assume we've been debugged and fall through to the less-reliable kill() test. Review by Tom Lane. |
||
---|---|---|
.. | ||
ipc.c | ||
ipci.c | ||
Makefile | ||
pmsignal.c | ||
procarray.c | ||
procsignal.c | ||
README | ||
shmem.c | ||
shmqueue.c | ||
sinval.c | ||
sinvaladt.c | ||
standby.c |
src/backend/storage/ipc/README Cache Invalidation Synchronization Routines =========================================== Mon Jul 18 11:09:22 PDT 1988 W.KLAS The cache synchronization is done using a message queue. Every backend can register a message which then has to be read by all backends. A message read by all backends is removed from the queue automatically. If a message has been lost because the buffer was full, all backends that haven't read this message will be told that they have to reset their cache state. This is done at the time when they try to read the message queue. The message queue is implemented as a shared buffer segment. Actually, the queue is a circle to allow fast inserting, reading (invalidate data) and maintaining the buffer.