I can understand the behavior. However, if new transactions are opened via new connections and are successfully executed, how can it be that these are also rolled back?, Or is that also an expected behavior?
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.Vielen Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
From: Laurenz Albe <laurenz.albe@cybertec.at> Date: Tuesday, 7. May 2024 at 13:22 To: Julius Ernesti <julius.ernesti@kpi4me.de>, pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org> Subject: Re: BUG #18457: Possible data loss needs to be evaluated
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).