From: Tom Lane <tgl@sss.pgh.pa.us>
To: enderstd@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers
Date: Mon, 25 Sep 2023 16:14:10 -0400
Message-ID: <262084.1695672850@sss.pgh.pa.us> (raw)
In-Reply-To: <18130-7a86a7356a75209d@postgresql.org>
References: <18130-7a86a7356a75209d@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, enderstd@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers
In-Reply-To: <262084.1695672850@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox