-
- Downloads
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.
Showing
- src/backend/postmaster/bgworker.c 27 additions, 55 deletionssrc/backend/postmaster/bgworker.c
- src/backend/storage/ipc/procsignal.c 1 addition, 10 deletionssrc/backend/storage/ipc/procsignal.c
- src/backend/storage/ipc/shm_mq.c 31 additions, 45 deletionssrc/backend/storage/ipc/shm_mq.c
- src/backend/tcop/postgres.c 1 addition, 3 deletionssrc/backend/tcop/postgres.c
- src/include/storage/procsignal.h 0 additions, 1 deletionsrc/include/storage/procsignal.h
- src/test/modules/test_shm_mq/setup.c 26 additions, 39 deletionssrc/test/modules/test_shm_mq/setup.c
Loading
Please register or sign in to comment