pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Noah Misch <noah@leadboat.com>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Avoid "you don't own a lock of type ExclusiveLock" in GRANT TABL
Date: Mon, 25 Nov 2024 22:43:34 +0000
Message-ID: <E1tFhnq-003Wc7-Rz@gemulon.postgresql.org> (raw)

Avoid "you don't own a lock of type ExclusiveLock" in GRANT TABLESPACE.

This WARNING appeared because SearchSysCacheLocked1() read
cc_relisshared before catcache initialization, when the field is false
unconditionally.  On the basis of reading false there, it constructed a
locktag as though pg_tablespace weren't relisshared.  Only shared
catalogs could be affected, and only GRANT TABLESPACE was affected in
practice.  SearchSysCacheLocked1() callers use one other shared-relation
syscache, DATABASEOID.  DATABASEOID is initialized by the end of
CheckMyDatabase(), making the problem unreachable for pg_database.

Back-patch to v13 (all supported versions).  This has no known impact
before v16, where ExecGrant_common() first appeared.  Earlier branches
avoid trouble by having a separate ExecGrant_Tablespace() that doesn't
use LOCKTAG_TUPLE.  However, leaving this unfixed in v15 could ensnare a
future back-patch of a SearchSysCacheLocked1() call.

Reported by Aya Iwata.

Discussion: https://postgr.es/m/OS7PR01MB11964507B5548245A7EE54E70EA212@OS7PR01MB11964.jpnprd01.prod.outlook.com

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/718af10dab446c2ae73fe027a9f65be69bcf2980

Modified Files
--------------
src/backend/utils/cache/syscache.c       | 15 ++++++++++-----
src/test/regress/expected/tablespace.out |  5 +++++
src/test/regress/sql/tablespace.sql      |  6 ++++++
3 files changed, 21 insertions(+), 5 deletions(-)



view thread (6+ messages)  latest in thread

Message-ID: <E1tFhnq-003Wc7-Rz@gemulon.postgresql.org>
Permalink:  ../E1tFhnq-003Wc7-Rz@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1tFhnq-003Wc7-Rz@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: noah@leadboat.com, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Avoid "you don't own a lock of type ExclusiveLock" in GRANT TABL
  In-Reply-To: <E1tFhnq-003Wc7-Rz@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox