Re: Pro et contra of preserving pg_proc oids during pg_upgrade - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Pro et contra of preserving pg_proc oids during pg_upgrade
Date
Msg-id CAKFQuwajchbptpSk-vRVN95BymYhAaib-fh4T_cHs-2mDXYgjQ@mail.gmail.com
Whole thread Raw
In response to Re: Pro et contra of preserving pg_proc oids during pg_upgrade  (Nikita Malakhov <hukutoc@gmail.com>)
List pgsql-hackers
On Thu, Oct 12, 2023 at 9:57 AM Nikita Malakhov <hukutoc@gmail.com> wrote:
Say, we have data processed by some user function and we want to keep reference to this function
in our data.

Then you need to keep the user-visible identifier of said function (schema+name+input argument types - you'd probably want to incorporate version into the name) in your user-space code.  Exposing runtime generated oids to user-space is not something I can imagine the system supporting.  It goes against the very definition of "implementation detail" that user-space code is not supposed to depend upon.

David J.

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Separate memory contexts for relcache and catcache
Next
From: Robert Haas
Date:
Subject: Re: Eager page freeze criteria clarification