diff options
| author | Amit Kapila <akapila@postgresql.org> | 2025-09-24 04:11:53 +0000 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2025-09-24 04:11:53 +0000 |
| commit | e41d954da6aa04f0a4453e566d3bcc064512d457 (patch) | |
| tree | 3e364b55d07b6591cdda74cd028e2f2d4cefd49a /src/backend/commands/foreigncmds.c | |
| parent | f83fe65f3fc1cae177f6c75f7b38eb951dd217b5 (diff) | |
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
Diffstat (limited to 'src/backend/commands/foreigncmds.c')
0 files changed, 0 insertions, 0 deletions