From: Laurenz Albe <laurenz.albe@cybertec.at>
To: julius.ernesti@kpi4me.de
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18457: Possible data loss needs to be evaluated
Date: Tue, 07 May 2024 13:22:13 +0200
Message-ID: <7aafc728c6928b1b3a6e6ddeae8ae59dd3f65261.camel@cybertec.at> (raw)
In-Reply-To: <18457-dc62fafe74c67bdd@postgresql.org>
References: <18457-dc62fafe74c67bdd@postgresql.org>
On Tue, 2024-05-07 at 08:35 +0000, PG Bug reporting form wrote:
> ERROR: current transaction is aborted, commands ignored until end of transaction block
>
> We are still trying to find out how this could have happened.
This is not a bug, it is expected behavior.
If a statement in a transaction causes an error, all subsequent
statements in that transaction will receive that message until
you end the transaction with ROLLBACK or COMMIT (which will also
roll back).
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, julius.ernesti@kpi4me.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18457: Possible data loss needs to be evaluated
In-Reply-To: <7aafc728c6928b1b3a6e6ddeae8ae59dd3f65261.camel@cybertec.at>
* 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