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

From Andres Freund
Subject Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers
Date
Msg-id 20231014023443.su2sreiluntso53k@awork3.anarazel.de
Whole thread Raw
In response to Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

On 2023-09-25 16:14:10 -0400, Tom Lane wrote:
> PG Bug reporting form <noreply@postgresql.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



pgsql-bugs by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used