From: | Matthias Apitz <guru(at)unixarea(dot)de> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to reset a server error '25P02 in_failed_sql_transaction' |
Date: | 2020-01-01 17:39:36 |
Message-ID: | 20200101173936.GA6796@c720-r342378 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
El día martes, diciembre 31, 2019 a las 10:06:22a. m. +0000, Patrick FICHE escribió:
> Hi,
>
> Which behavior are you looking for ?
> If you want the following statements to succeed, I guess that you don't want to be in a transaction context.
> In this case, you should have a look at the following link : https://www.postgresql.org/docs/11/ecpg-commands.html
> By default, the AUTOCOMMIT is OFF but you can set it to ON and it should solve your issue as only explicit transactions will keep a transaction context.
>
> Regards,
Hi,
To summarize the different hints:
- terminate the relevant backend process with pg_terminate_backend()
- issue ROLLBACK
- set AUTOCOMMIT TO ON
Thanks, I will try these hints in the order from bottom to up, and as
well to close/re-open the connection to the server, without the GUI
client will note this; every GUI client has its own application server:
GUI (Java in Windows) --> application server (ESQL/C Linux) --> PGserver
Thanks (and btw: Happy New Jear!)
matthias
--
Matthias Apitz, ✉ guru(at)unixarea(dot)de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
"Glaube wenig, hinterfrage alles, denke selbst: Wie man Manipulationen durchschaut"
"Believe little, scrutinise all, think by your own: How see through manipulations"
ISBN-10: 386489218X
From | Date | Subject | |
---|---|---|---|
Next Message | Sonam Sharma | 2020-01-02 07:15:10 | Schema dump |
Previous Message | Mike Lissner | 2019-12-31 23:51:25 | How to shorten a chain of logically replicated servers |