Re: unexpected chunk number 2 (expected 0) for toast value ... inpg_toast_18536 - Mailing list pgsql-general

From Andres Freund
Subject Re: unexpected chunk number 2 (expected 0) for toast value ... inpg_toast_18536
Date
Msg-id 20200316194453.tf3dlgovim6lpfbc@alap3.anarazel.de
Whole thread Raw
In response to Re: unexpected chunk number 2 (expected 0) for toast value ... in pg_toast_18536  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: unexpected chunk number 2 (expected 0) for toast value ... inpg_toast_18536
List pgsql-general
Hi,

On 2020-03-15 20:11:18 -0400, Tom Lane wrote:
> Unfortunately, it seems like you can't do that either, short of
> hacking up the backend or writing some custom C code, because the
> executor won't let you open a toast table as result relation :-(.
> I wonder if we should change it to allow that when
> allow_system_table_mods is true?  This isn't the first time we've
> seen people need to be able to do surgery on a toast table.

I'd be mildly in favor. But it's considerably more than just the
executor check that'd need to change. We don't the right thing for toast
relations in plenty places right now, because we just check for
RELKIND_RELATION - which will break junkvars etc.

Greetings,

Andres Freund



pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: unexpected chunk number 2 (expected 0) for toast value ... inpg_toast_18536
Next
From: Andres Freund
Date:
Subject: Re: unexpected chunk number 2 (expected 0) for toast value ... inpg_toast_18536