Re: BUG #19519: REPACK can fail due to missing chunk for toast value - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #19519: REPACK can fail due to missing chunk for toast value
Date
Msg-id ak16dMkUP1pS0rCn@paquier.xyz
Whole thread
Responses Re: BUG #19519: REPACK can fail due to missing chunk for toast value
List pgsql-bugs
On Tue, Jul 07, 2026 at 10:40:12PM +0530, Srinath Reddy Sadipiralla wrote:
> I quickly reviewed the core logic of treating the missing
> chunks as dead and LGTM will further look into this and test.

Thanks for that.  This is tricky and invasive enough that this
warrants more eyes.

One thing that I still don't like much in the patch as written is my
use of a missing_ok argument, which feels super confusing as it
applies only to the underlying external TOAST, if the relation has
any.  I'd be tempted to rewrite this portion of the patch with a
uint32 flags.  Even if we assign one value for now (say MISSING_TOAST,
MISSING_TOAST_OK or whatever), it would allow more flexibility on ABI
grounds if we want more like states in the future across this portion
of the stack.  Again, I strongly doubt that we will be able to
backpatch any of that.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Thom Brown
Date:
Subject: Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
Next
From: surya poondla
Date:
Subject: Re: BUG #19382: Server crash at __nss_database_lookup