Add a syscache on pg_extension.oid. An upcoming patch requires this cache so that it can track updates in the pg_extension catalog. So far though, the EXTENSIONOID cache only exists in v18 and up (see 490f869d9). We can add it in older branches without an ABI break, if we are careful not to disturb the numbering of existing syscache IDs.
In v16 and before, that just requires adding the new ID at the end of the hand-assigned enum list, ignoring our convention about alphabetizing the IDs. But in v17, genbki.pl enforces alphabetical order of the IDs listed in MAKE_SYSCACHE macros. We can fake it out by calling the new cache ZEXTENSIONOID. Note that adding a syscache does change the required contents of the relcache init file (pg_internal.init). But that isn't problematic since we blow those away at postmaster start for other reasons. Author: Tom Lane <[email protected]> Reviewed-by: Noah Misch <[email protected]> Security: CVE-2026-2004 Backpatch-through: 14-17 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/d484bc26013caedd0b210bddfcec43c2ab6fa649 Modified Files -------------- src/backend/utils/cache/syscache.c | 8 ++++++++ src/include/utils/syscache.h | 6 ++++-- 2 files changed, 12 insertions(+), 2 deletions(-)
