Re: Preserve subscription OIDs during pg_upgrade

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Preserve subscription OIDs during pg_upgrade
Дата
Msg-id ZeZvjmxxKVd_lvFW@momjian.us
обсуждение исходный текст
Ответ на Re: Preserve subscription OIDs during pg_upgrade  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Mon, Feb 26, 2024 at 09:51:40AM +0530, Robert Haas wrote:
> > I am not sure that it is a good idea to relax that for PG17 at this
> > stage of the development cycle, though, as we have already done a lot
> > in this area for pg_upgrade and it may require more tweaks during the
> > beta period depending on the feedback received, so I would suggest to
> > do more improvements for the 18 cycle instead once we have a cleaner
> > picture of the whole.
> 
> That's fair.
> 
> I want to say that, unlike Tom, I'm basically in favor of preserving
> OIDs in more places across updates. It seems to have little downside
> and improve the understandability of the outcome. But that's separate
> from whether it is a good idea to build on that infrastructure in any
> particular way in the time we have left for this release.

Yes, the _minimal_ approach has changed in the past few years to make
pg_upgrade debugging easier.  The original design was ultra-conservative
where it could be, considering how radical the core functionality was.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Fix race condition in InvalidatePossiblyObsoleteSlot()
Следующее
От: Amit Langote
Дата:
Сообщение: Re: remaining sql/json patches