Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: enderstd@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2023-10-14T02:34:43Z
Lists: 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
Commits
-
Fix bulk table extension when copying into multiple partitions
- 0002feb82096 16.1 landed
- 22655aa23132 17.0 landed