Make deadlock_timeout PGC_SUSET rather than PGC_SIGHUP.
Robert Haas <rhaas@postgresql.org>
Make deadlock_timeout PGC_SUSET rather than PGC_SIGHUP. This allows deadlock_timeout to be reduced for transactions that are particularly likely to be involved in a deadlock, thus detecting it more quickly. It is also potentially useful as a poor-man's deadlock priority mechanism: a transaction with a high deadlock_timeout is less likely to be chosen as the victim than one with a low deadlock_timeout. Since that could be used to game the system, we make this PGC_SUSET rather than PGC_USERSET. At some point, it might be worth thinking about a more explicit priority mechanism, since using this is far from fool-proof. But let's see whether there's enough use case to justify the additional work before we go down that route. Noah Misch, reviewed by Shigeru Hanada
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/config.sgml | modified | +2 −1 |
| src/backend/utils/misc/guc.c | modified | +2 −2 |