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

From Nikita Malakhov
Subject Re: Pro et contra of preserving pg_proc oids during pg_upgrade
Date
Msg-id CAN-LCVNKA-55F+8LvVVXqazmkywO60sROJyDoc0jARrTQ3go7g@mail.gmail.com
Whole thread Raw
In response to Re: Pro et contra of preserving pg_proc oids during pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Pro et contra of preserving pg_proc oids during pg_upgrade  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: Pro et contra of preserving pg_proc oids during pg_upgrade  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
Hi!

Say, we have data processed by some user function and we want to keep reference to this function
in our data. In this case we have two ways - first - store string output of regprocedure, which is not
very convenient, and the second - store its OID, which requires slight modification of pg_upgrade
(pg_dump and func/procedure creation function).

I've read previous threads about using regproc, and agree that this is not a very good case anyway,
but I haven't found any serious obstacles that forbid modifying pg_upgrade this way.

--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Performance degradation on concurrent COPY into a single relation in PG16.
Next
From: Andres Freund
Date:
Subject: Re: Separate memory contexts for relcache and catcache