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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: enderstd(at)gmail(dot)com
Cc: 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-09-25 20:14:10
Message-ID: 262084.1695672850@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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].

regards, tom lane

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2023-09-25 21:24:12 Re: BUG #18129: GiST index produces incorrect query results
Previous Message Andres Freund 2023-09-25 17:45:04 Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"