| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: Preserve subscription OIDs during pg_upgrade |
| Date: | 2024-03-05 13:28:26 |
| Message-ID: | CAJ7c6TMNq8QZg2ukunO3w9=gzJSh3ZwQPGj2OCECfsbp4Nnc5Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> It will be better to preserve them as it will be easier to
> compare subscription related objects in pg_subscription and
> pg_subscription_rel in the old and new clusters.
IMO it would be helpful if you could give a little bit more context on
why/when this is useful. Personally I find it somewhat difficult to
imagine a case when I really need to compare Oids of subscriptions
between old and new clusters.
If we commit to such a guarantee it will lay a certain burden on the
community in the long run and the benefits are not quite clear, to me
at least. If we are talking about giving such a guarantee only once
the value of this is arguably low.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-03-05 13:43:33 | Re: pg_upgrade --copy-file-range |
| Previous Message | Bertrand Drouvot | 2024-03-05 13:22:23 | Re: Missing LWLock protection in pgstat_reset_replslot() |