Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: enderstd(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers
Date: 2023-10-14 02:34:43
Message-ID: 20231014023443.su2sreiluntso53k@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2023-09-25 16:14:10 -0400, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > I'm trying to copy a CSV file to a table and it errors out with different
> > error messages every time:
>
> Thank you for the report and reproducible test case! It looks to me
> like this is probably a bug in our new logic for extending tables
> more than one block at a time, and the connection to triggers is
> accidental. I brought it up in a thread that was already discussing
> the extension logic [1].

It indeed was. I've pushed the fix for that now, as discussed in that other
thread.

Thanks for the report and reproducer!

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2023-10-14 07:00:00 Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Previous Message Alexander Lakhin 2023-10-13 15:00:00 Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used