| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 |
| Date: | 2021-08-15 14:44:55 |
| Message-ID: | 20210815144455.GQ10479@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans Buschmann | 2021-08-15 14:58:59 | PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode |
| Previous Message | Andy Fan | 2021-08-15 14:33:13 | Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series) |