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

From Michael Paquier
Subject pgsql: Fix one-off issue with cache ID in objectaddress.c
Date
Msg-id E1vsUo5-001M17-25@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Álvaro Herrera
Date:
Subject: pgsql: Use a bitmask for ExecInsertIndexTuples options
Next
From: Michael Paquier
Date:
Subject: pgsql: Add concept of invalid value to SysCacheIdentifier