agora inbox for pgsql-committers@postgresql.org
help / color / mirror / Atom feedFrom: Andrew Dunstan <andrew@dunslane.net>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix concurrency issues with DROP TABLESPACE
Date: Wed, 09 Sep 2026 15:34:50 +0000
Message-ID: <E1x4KK1-0000000499B-2Z5x@gemulon.postgresql.org> (raw)
Fix concurrency issues with DROP TABLESPACE
DROP TABLESPACE checked pg_shdepend for dependent objects without
first locking the tablespace. A concurrent command that recorded a
shared dependency on the tablespace right after that check could still
commit, leaving an object whose pg_shdepend entry (or, for a relation,
pg_class.reltablespace) pointed to a tablespace that no longer existed.
Close the race by having DropTableSpace() take an AccessExclusiveLock
on the tablespace before calling checkSharedDependencies(). That
conflicts with the AccessShareLock shdepLockAndCheckObject() takes when
recording a new dependency, so the loser of the race blocks and
rechecks once the winner commits.
That AccessExclusiveLock creates a new deadlock: ALTER TABLESPACE
RENAME/SET and the internal ACL/owner updates in DROP OWNED and
REASSIGN OWNED touched the catalog tuple without locking the
tablespace, risking a lock-order cycle with DROP. Fix by taking an
AccessShareLock first in all four paths, rechecking pg_shdepend after
any wait in the DROP OWNED and REASSIGN OWNED cases. GRANT, REVOKE,
and ALTER TABLESPACE ... OWNER TO already lock the object.
Add isolation tests covering both orderings of the original race
(dependency-first and drop-first) and all four previously-unlocked
update paths.
Author: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Reviewed-by: Andrew Dunstan <andrew@dunslane.net>
Discussion: https://postgr.es/m/CAJTYsWXjAQFnGKzXsht3XK8KHhyhontwFJw4JAHsUSfs_ptR4g@mail.gmail.com
Backpatch-through: 14
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/749dd8d1f2cf8ae261122b8db397bc5dafcb99bb
Modified Files
--------------
src/backend/catalog/pg_shdepend.c | 42 ++++++++--
src/backend/commands/tablespace.c | 17 +++-
.../expected/tablespace-dependency-locking.out | 84 +++++++++++++++++++
src/test/isolation/isolation_schedule | 1 +
.../specs/tablespace-dependency-locking.spec | 98 ++++++++++++++++++++++
5 files changed, 235 insertions(+), 7 deletions(-)
view thread (7+ messages) latest in thread
Message-ID: <E1x4KK1-0000000499B-2Z5x@gemulon.postgresql.org>
Permalink: ../E1x4KK1-0000000499B-2Z5x@gemulon.postgresql.org/
Also on: postgresql.org/message-id/E1x4KK1-0000000499B-2Z5x@gemulon.postgresql.org
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: andrew@dunslane.net, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix concurrency issues with DROP TABLESPACE
In-Reply-To: <E1x4KK1-0000000499B-2Z5x@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox