Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce)
От | Tom Lane |
---|---|
Тема | Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce) |
Дата | |
Msg-id | 347096.1629821040@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce)
Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce) |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, Aug 23, 2021 at 8:29 PM Bruce Momjian <bruce@momjian.us> wrote: >> I assume this patch is not going to be applied until there is an actual >> use case for preserving these values. > ... > That being said, if you or somebody else thinks that this is a bad > idea or that the reasons offered up until now are insufficient, feel > free to make that argument. I just work here... Per upthread discussion, it seems impractical to fully guarantee that database OIDs match, which seems to mean that the whole premise collapses. Like Bruce, I want to see a plausible use case justifying any partial-guarantee scenario before we add more complication (= bugs) to pg_upgrade. regards, tom lane
В списке pgsql-hackers по дате отправления: