| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Imran Zaheer <imran(dot)zhir(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru> |
| Subject: | Re: BUG #19519: REPACK can fail due to missing chunk for toast value |
| Date: | 2026-07-07 22:15:16 |
| Message-ID: | ak16dMkUP1pS0rCn@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | surya poondla | 2026-07-07 23:20:55 | Re: BUG #19382: Server crash at __nss_database_lookup |
| Previous Message | Srinath Reddy Sadipiralla | 2026-07-07 17:10:12 | Re: BUG #19519: REPACK can fail due to missing chunk for toast value |