Re: PostgreSQL server "idle in transaction"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Matthias Apitz <guru(at)unixarea(dot)de>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL server "idle in transaction"
Date: 2022-11-15 15:28:11
Message-ID: 1070974.1668526091@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 11/15/22 04:28, Matthias Apitz wrote:
>> I have below the full ESQL/C log and do not understand, why the
>> PostgreSQL server is thinking "idle in transaction". For me with the
>> "COMMIT" on the line below marked with ^^^^^ the transaction was closed.

> From your log:

> [6978] [15.11.2022 11:05:50:172]: ECPGtrans on line 1211: action
> "commit"; connection "testdb"
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [6978] [15.11.2022 11:05:50:173]: ecpg_execute on line 543: query:
> select name from pg_cursors where name = $1 ; with 1 parameter(s) on
> connection testdb

> So that query is being executed after the COMMIT.

Right. By default, ecpg would start a new transaction block for that.
See

https://www.postgresql.org/docs/current/ecpg-commands.html#ECPG-TRANSACTIONS

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karthik Jagadish (kjagadis) 2022-11-15 15:46:06 Index not getting cleaned even though vacuum is running
Previous Message Adrian Klaver 2022-11-15 15:08:32 Re: PostgreSQL server "idle in transaction"