Remove set_latch_on_sigusr1 flag.
Robert Haas <rhaas@postgresql.org>
Remove set_latch_on_sigusr1 flag. This flag has proven to be a recipe for bugs, and it doesn't seem like it can really buy anything in terms of performance. So let's just *always* set the process latch when we receive SIGUSR1 instead of trying to do it only when needed. Per my recent proposal on pgsql-hackers.
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/postmaster/bgworker.c | modified | +27 −55 |
| src/backend/storage/ipc/procsignal.c | modified | +1 −10 |
| src/backend/storage/ipc/shm_mq.c | modified | +31 −45 |
| src/backend/tcop/postgres.c | modified | +1 −3 |
| src/include/storage/procsignal.h | modified | +0 −1 |
| src/test/modules/test_shm_mq/setup.c | modified | +26 −39 |