From: | Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17669: Invalid TOAST pointer in PL/pgSQL variable |
Date: | 2022-10-28 14:16:02 |
Message-ID: | cf30bc3d-fc00-351b-2c1f-f24418881ccb@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 28.10.2022 16:43, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> postgres=# select f();
>> ERROR: missing chunk number 0 for toast value 24727 in pg_toast_24722
>
> To prevent that, every fetch into a plpgsql variable would have
> to immediately detoast the value, in case somebody did something
> as weird as dropping/truncating the table later in the function.
> That's an awfully expensive bit of protection. We do in fact
> do it like that in procedures (more specifically, in non-atomic
> contexts), so a possible workaround for you is to make this a
> procedure not a function. I'm disinclined to change it otherwise.
Thank you for explaining.
--
Sergey Shinderuk https://postgrespro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2022-10-28 14:36:59 | Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios |
Previous Message | Tom Lane | 2022-10-28 13:43:00 | Re: BUG #17669: Invalid TOAST pointer in PL/pgSQL variable |