Re: duplicate function oid symbols
John Naylor <john.naylor@enterprisedb.com>
From: John Naylor <john.naylor@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-10-27T21:40:09Z
Lists: pgsql-hackers
Attachments
- v1-0001-Use-the-standard-symbol-for-the-builtin-function-.patch (application/octet-stream) patch v1-0001
On Tue, Oct 27, 2020 at 9:51 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > John Naylor <john.naylor@enterprisedb.com> writes: > > I noticed that the table AM abstraction introduced the symbol > > HEAP_TABLE_AM_HANDLER_OID, although we already have a convention for > > defining symbols automatically for builtin functions, which in this case > is > > (currently unused) F_HEAP_TABLEAM_HANDLER. > > Yeah, that seems wrong. I'd just remove HEAP_TABLE_AM_HANDLER_OID. > As long as we're not back-patching the change, it seems like a very > minor thing to fix, if anyone outside core is referencing the old name. > Ok, here is a patch to fix that, and also throw an error if pg_proc.dat has an explicitly defined symbol. -- John Naylor EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Don't use custom OID symbols in pg_type.dat, either.
- f90149e6285a 14.0 landed
-
Don't use custom OID symbols in pg_proc.dat.
- 36b93121436c 14.0 landed