Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Дата
Msg-id 2595981.1621203681@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes:
> On Sun, May 16, 2021 at 1:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> And the reason oldestXID contains that is that pg_upgrade applied
>> pg_resetwal, which does this:
>> * For the moment, just set oldestXid to a value that will force
>> * immediate autovacuum-for-wraparound.

> This same pg_resetwal code has probably caused quite a few problems on
> pg_upgrade'd databases:
> https://postgr.es/m/20210423234256.hwopuftipdmp3okf@alap3.anarazel.de

Hm, yeah.  I'm not sure if transferring the value forward from the
old cluster is entirely safe, but if it is, that seems like a
promising route to a fix.  (We should still have more sanity checking
around the GlobalVis code, though.)

            regards, tom lane



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Следующее
От: Andres Freund
Дата:
Сообщение: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619