pgsql: Fix REPACK decoding worker not cleaned up on FATAL exit - Mailing list pgsql-committers

From Álvaro Herrera
Subject pgsql: Fix REPACK decoding worker not cleaned up on FATAL exit
Date
Msg-id E1wPPQE-000IqK-00@gemulon.postgresql.org
Whole thread
List pgsql-committers
Fix REPACK decoding worker not cleaned up on FATAL exit

When the launching backend of REPACK (CONCURRENTLY) is terminated via
pg_terminate_backend(), ProcDiePending causes ereport(FATAL) which
bypasses PG_FINALLY blocks.  As a result, stop_repack_decoding_worker()
is never called, leaving the decoding worker running indefinitely and
holding its temporary replication slot.

Fix by using PG_ENSURE_ERROR_CLEANUP, which handles both ERROR and
FATAL exits.

Author: Baji Shaik <baji.pgdev@gmail.com>
Reviewed-by: Sami Imseih <samimseih@gmail.com>
Reviewed-by: Álvaro Herrera <alvherre@kurilemu.de>
Discussion: https://postgr.es/m/CA+fm-RNoPxL2N7db_A0anMXV_aDu6jWj4PNOPtMtBUAPDPvSXQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/0160143ad9a686a7e705348da1f90e63a2a31536

Modified Files
--------------
src/backend/commands/repack.c | 42 +++++++++++++++++++++++++-----------------
1 file changed, 25 insertions(+), 17 deletions(-)


pgsql-committers by date:

Previous
From: Alexander Korotkov
Date:
Subject: pgsql: Fix SPLIT PARTITION range bound validation with DEFAULT
Next
From: Fujii Masao
Date:
Subject: pgsql: pg_recvlogical: Add tests for output file permissions