Subject: Re: display previous query string of idle-in-transaction
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tatsuhito Kasahara <kasahara.tatsuhito@oss.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org
In-Reply-To: <49CC8524.4090103@oss.ntt.co.jp>
References: <49C9F49B.8020003@oss.ntt.co.jp>
	<1238091273.16568.530.camel@ebony.2ndQuadrant>
	<49CC75E3.7010101@oss.ntt.co.jp>
	<1238139418.16568.555.camel@ebony.2ndQuadrant>
	<49CC8524.4090103@oss.ntt.co.jp>
Content-Type: text/plain
Date: Fri, 27 Mar 2009 08:07:11 +0000
Message-Id: <1238141231.16568.574.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


On Fri, 2009-03-27 at 16:49 +0900, Tatsuhito Kasahara wrote:
> Simon Riggs wrote:
> >> Does that answer your question ?
> > 
> > Not really. I want to understand the actual problem with
> > idle-in-transaction so we can consider all ways to solve it, rather than
> > just focus on one method.
> "idle in transaction timeout" feature may be one of the ways.
> But I have no specific idea about it now.

Or take it further back still and think about why "idle in transaction"
occurs at all and fix *that*. Maybe not in Postgres at all, possibly in
the driver or even higher up client stack.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support