pgsql: Fix one-off issue with cache ID in objectaddress.c

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix one-off issue with cache ID in objectaddress.c
Date: 2026-02-17 23:48:42
Message-ID: E1vsUo5-001M17-25@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix one-off issue with cache ID in objectaddress.c

get_catalog_object_by_oid_extended() has been doing a syscache lookup
when given a cache ID strictly higher than 0, which is wrong because the
first valid value of SysCacheIdentifier is 0.

This issue had no consequences, as the first value assigned in the
enum SysCacheIdentifier is AGGFNOID, which is not used in the object
type properties listed in objectaddress.c. Even if an ID of 0 was
hypotherically given, the code would still work with a less efficient
heap-or-index scan.

Discussion: https://postgr.es/m/aZTr_R6JGmqokUBb@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f7df12a66cc90ed12d24edba31eeedfb546ef14c

Modified Files
--------------
src/backend/catalog/objectaddress.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2026-02-18 00:26:35 pgsql: Add concept of invalid value to SysCacheIdentifier
Previous Message Álvaro Herrera 2026-02-17 17:46:26 pgsql: Use a bitmask for ExecInsertIndexTuples options