diff options
| author | Robert Haas <rhaas@postgresql.org> | 2015-10-09 14:31:04 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2015-10-09 14:31:04 -0400 |
| commit | db0f6cad4884bd4c835156d3a720d9a79dbd63a9 (patch) | |
| tree | e16029e0e2a001eb34096daeb3c8100e2afb0a1d /src/include/storage/procsignal.h | |
| parent | b7aac36245261eba9eb7d18561ce44220b361959 (diff) | |
| download | postgresql-db0f6cad4884bd4c835156d3a720d9a79dbd63a9.tar.gz postgresql-db0f6cad4884bd4c835156d3a720d9a79dbd63a9.zip | |
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.
Diffstat (limited to 'src/include/storage/procsignal.h')
| -rw-r--r-- | src/include/storage/procsignal.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/include/storage/procsignal.h b/src/include/storage/procsignal.h index af1a0cd71f2..50ffb13e1f2 100644 --- a/src/include/storage/procsignal.h +++ b/src/include/storage/procsignal.h @@ -55,6 +55,5 @@ extern int SendProcSignal(pid_t pid, ProcSignalReason reason, BackendId backendId); extern void procsignal_sigusr1_handler(SIGNAL_ARGS); -extern PGDLLIMPORT bool set_latch_on_sigusr1; #endif /* PROCSIGNAL_H */ |