]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b7aac36) | patch
Remove set_latch_on_sigusr1 flag.
authorRobert Haas <rhaas@postgresql.org>
Fri, 9 Oct 2015 18:31:04 +0000 (14:31 -0400)
committerRobert Haas <rhaas@postgresql.org>
Fri, 9 Oct 2015 18:31:04 +0000 (14:31 -0400)
commitdb0f6cad4884bd4c835156d3a720d9a79dbd63a9
treee16029e0e2a001eb34096daeb3c8100e2afb0a1dtree | snapshot
parentb7aac36245261eba9eb7d18561ce44220b361959commit | diff
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.
src/backend/postmaster/bgworker.c diff | blob | history
src/backend/storage/ipc/procsignal.c diff | blob | history
src/backend/storage/ipc/shm_mq.c diff | blob | history
src/backend/tcop/postgres.c diff | blob | history
src/include/storage/procsignal.h diff | blob | history
src/test/modules/test_shm_mq/setup.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.