Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
От | Justin Pryzby |
---|---|
Тема | Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 |
Дата | |
Msg-id | 20210815144455.GQ10479@telsasoft.com обсуждение исходный текст |
Ответ на | Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
|
Список | pgsql-hackers |
On Sun, May 16, 2021 at 04:23:02PM -0400, Tom Lane wrote: > 1. Fix FullXidRelativeTo to be a little less trusting. It'd > probably be sane to make it return FirstNormalTransactionId > when it'd otherwise produce a wrapped-around FullXid, but is > there any situation where we'd want it to throw an error instead? > > 2. Change pg_resetwal to not do the above. It's not entirely > apparent to me what business it has trying to force > autovacuum-for-wraparound anyway, but if it does need to do that, > can we devise a less klugy method? > > It also seems like some assertions in procarray.c would be a > good idea. With the attached patch, we get through core > regression just fine, but the pg_upgrade test fails immediately > after the "Resetting WAL archives" step. #2 is done as of 74cf7d46a. Is there a plan to include Tom's procarray assertions ? -- Justin
В списке pgsql-hackers по дате отправления: