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/backend/tcop/postgres.c | |
| 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/backend/tcop/postgres.c')
| -rw-r--r-- | src/backend/tcop/postgres.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c index aee13aec757..d30fe35c14f 100644 --- a/src/backend/tcop/postgres.c +++ b/src/backend/tcop/postgres.c @@ -2825,9 +2825,7 @@ RecoveryConflictInterrupt(ProcSignalReason reason) /* * Set the process latch. This function essentially emulates signal * handlers like die() and StatementCancelHandler() and it seems prudent - * to behave similarly as they do. Alternatively all plain backend code - * waiting on that latch, expecting to get interrupted by query cancels et - * al., would also need to set set_latch_on_sigusr1. + * to behave similarly as they do. */ SetLatch(MyLatch); |