diff options
| author | Noah Misch <noah@leadboat.com> | 2024-11-25 14:42:35 -0800 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2024-11-25 14:42:35 -0800 |
| commit | 4ba84de459532a7a79616e756f8bfd45ba4b8048 (patch) | |
| tree | 6e0566ec4bb6f57519d0a945e33787edd967f3f8 /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 96a81c1be929d122719bd289f6e24824f37e1ff6 (diff) | |
| download | postgresql-4ba84de459532a7a79616e756f8bfd45ba4b8048.tar.gz postgresql-4ba84de459532a7a79616e756f8bfd45ba4b8048.zip | |
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
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions