diff options
| author | Amit Kapila <akapila@postgresql.org> | 2025-08-01 07:58:48 +0000 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2025-08-01 07:58:48 +0000 |
| commit | 2ab2d6f970584b7ca60cfdf6569336903aa88db5 (patch) | |
| tree | 96e2967e062d8d769227cb63b1ad80eed420f5b9 /src/tools/msvc/dummylib/Win32API | |
| parent | ca09ef3a6aa69a1250bc83e6d9517f28a2ff181c (diff) | |
| download | postgresql-master.tar.gz postgresql-master.zip | |
A deadlock can occur when the DDL command and the apply worker acquire
catalog locks in different orders while dropping replication origins.
The issue is rare in PG16 and higher branches because, in most cases, the
tablesync worker performs the origin drop in those branches, and its
locking sequence does not conflict with DDL operations.
This patch ensures consistent lock acquisition to prevent such deadlocks.
As per buildfarm.
Reported-by: Alexander Lakhin <exclusion@gmail.com>
Author: Ajin Cherian <itsajin@gmail.com>
Reviewed-by: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Reviewed-by: vignesh C <vignesh21@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Backpatch-through: 14, where it was introduced
Discussion: https://postgr.es/m/bab95e12-6cc5-4ebb-80a8-3e41956aa297@gmail.com
Diffstat (limited to 'src/tools/msvc/dummylib/Win32API')
0 files changed, 0 insertions, 0 deletions