From: Tatsuhito Kasahara <kasahara.tatsuhito@oss.ntt.co.jp>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: display previous query string of idle-in-transaction
Date: Fri, 27 Mar 2009 15:44:51 +0900
Message-ID: <49CC75E3.7010101@oss.ntt.co.jp> (raw)
In-Reply-To: <1238091273.16568.530.camel@ebony.2ndQuadrant>
References: <49C9F49B.8020003@oss.ntt.co.jp>
<1238091273.16568.530.camel@ebony.2ndQuadrant>
Simon Riggs wrote:
>> If we can also check previous query_string of idle-in-transaction,
>> it is useful for analysis of long transaction problem.
>
> I'm more interested in the problem itself. Why do you think there is a
> problem and why does knowing this help you? I had similar problems
> recently, so I'm interested in thoughts around this.
In many case, applications don't know what queries they are doing.
So, if a long transaction problem (unworking defragmnetation by HOT and
VACUUM) occured, I don't understand which application is the cause with
only "<IDLE> in transaction" message.
But if I can also check last query string, I guess which apllication
do that and point out the problem point.
# As I said, I think a long transaction is not a problem itself.
Does that answer your question ?
Best regards,
--
Tatsuhito Kasahara
kasahara.tatsuhito@oss.ntt.co.jp
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-hackers@postgresql.org
Cc: kasahara.tatsuhito@oss.ntt.co.jp, simon@2ndQuadrant.com
Subject: Re: display previous query string of idle-in-transaction
In-Reply-To: <49CC75E3.7010101@oss.ntt.co.jp>
* 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