| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 20:30:53 |
| Message-ID: | CAN-LCVNzZo+dzgBJjYFHAajjopHiHExbBPpkT_azdkESy4PsMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I've already implemented preserving PG_PROC oids during pg_upgrade
in a way like relfilenodes, etc, actually, it is quite simple, and on the
first
look there are no any problems.
About using surrogate key - this feature is more for data generated by
the DBMS itself, i.e. data processed by some extension and saved
and re-processed automatically or by user's request, but without bothering
user with these internal keys.
The main question - maybe, are there pitfalls of which I am not aware of?
Thanks for your replies!
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2023-10-12 21:46:41 | Re: Pro et contra of preserving pg_proc oids during pg_upgrade |
| Previous Message | Robert Haas | 2023-10-12 20:16:40 | Re: Pro et contra of preserving pg_proc oids during pg_upgrade |