Re: visibility map corruption
От | Bruce Momjian |
---|---|
Тема | Re: visibility map corruption |
Дата | |
Msg-id | 20210706224910.GF26994@momjian.us обсуждение исходный текст |
Ответ на | Re: visibility map corruption (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: visibility map corruption
Re: visibility map corruption |
Список | pgsql-hackers |
On Tue, Jul 6, 2021 at 03:46:48PM -0700, Peter Geoghegan wrote: > On Tue, Jul 6, 2021 at 3:30 PM Bruce Momjian <bruce@momjian.us> wrote: > > Yes, I can, though it seems like a much bigger issue than pg_upgrade. > > I will be glad to dig into it. > > I'm not sure what you mean by that. Technically this would be an issue > for any program that uses "pg_resetwal -x" in the way that pg_upgrade > does, with those same expectations. But isn't pg_upgrade the only > known program that behaves like that? > > I don't see any reason why this wouldn't be treated as a pg_upgrade > bug in the release notes, regardless of the exact nature or provenance > of the issue -- the pg_upgrade framing seems useful because this is a > practical problem for pg_upgrade users alone. Have I missed something? My point is that there are a lot internals involved here that are not part of pg_upgrade, though it probably only affects pg_upgrade. Anyway, Bertrand patch seems to have what I need. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
В списке pgsql-hackers по дате отправления: