| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Pro et contra of preserving pg_proc oids during pg_upgrade |
| Date: | 2023-10-12 16:56:32 |
| Message-ID: | CAN-LCVNKA-55F+8LvVVXqazmkywO60sROJyDoc0jARrTQ3go7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-10-12 17:01:05 | Re: Separate memory contexts for relcache and catcache |
| Previous Message | Andres Freund | 2023-10-12 16:24:19 | Re: Performance degradation on concurrent COPY into a single relation in PG16. |