Postgres Pro
Downloads
Home   >   mailing lists

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 Tom Lane
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 262084.1695672850@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers
List pgsql-bugs
Tree view 
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].

            regards, tom lane

[1] https://www.postgresql.org/message-id/257696.1695670946%40sss.pgh.pa.us

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
Next
From: Heikki Linnakangas
Date:
Subject: Re: BUG #18129: GiST index produces incorrect query results