Re: BUG #18457: Possible data loss needs to be evaluated

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: julius(dot)ernesti(at)kpi4me(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18457: Possible data loss needs to be evaluated
Date: 2024-05-07 11:22:13
Message-ID: 7aafc728c6928b1b3a6e6ddeae8ae59dd3f65261.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Julius Ernesti 2024-05-07 11:31:36 Re: BUG #18457: Possible data loss needs to be evaluated
Previous Message Laurenz Albe 2024-05-07 11:18:47 Re: BUG #18458: SQL Error [XX000]: ERROR: cache lookup failed for type 0