mirror of
https://github.com/postgres/postgres.git
synced 2025-11-10 17:42:29 +03:00
Fix LOCK_TIMEOUT handling during parallel apply.
Previously, the parallel apply worker used SIGINT to receive a graceful shutdown signal from the leader apply worker. However, SIGINT is also used by the LOCK_TIMEOUT handler to trigger a query-cancel interrupt. This overlap caused the parallel apply worker to miss LOCK_TIMEOUT signals, leading to incorrect behavior during lock wait/contention. This patch resolves the conflict by switching the graceful shutdown signal from SIGINT to SIGUSR2. Reported-by: Zane Duffield <duffieldzane@gmail.com> Diagnosed-by: Zhijie Hou <houzj.fnst@fujitsu.com> Author: Hayato Kuroda <kuroda.hayato@fujitsu.com> Reviewed-by: Amit Kapila <amit.kapila16@gmail.com> Backpatch-through: 16, where it was introduced Discussion: https://postgr.es/m/CACMiCkXyC4au74kvE2g6Y=mCEF8X6r-Ne_ty4r7qWkUjRE4+oQ@mail.gmail.com
This commit is contained in:
@@ -94,9 +94,8 @@ SignalHandlerForCrashExit(SIGNAL_ARGS)
|
||||
* shut down and exit.
|
||||
*
|
||||
* Typically, this handler would be used for SIGTERM, but some processes use
|
||||
* other signals. In particular, the checkpointer exits on SIGUSR2, and the WAL
|
||||
* writer and the logical replication parallel apply worker exits on either
|
||||
* SIGINT or SIGTERM.
|
||||
* other signals. In particular, the checkpointer and parallel apply worker
|
||||
* exit on SIGUSR2, and the WAL writer exits on either SIGINT or SIGTERM.
|
||||
*
|
||||
* ShutdownRequestPending should be checked at a convenient place within the
|
||||
* main loop, or else the main loop should call ProcessMainLoopInterrupts.
|
||||
|
||||
Reference in New Issue
Block a user