Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 041DE632549 for ; Fri, 27 Mar 2009 06:48:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 05720-06 for ; Fri, 27 Mar 2009 06:48:00 -0300 (ADT) Received: from mx3.hub.org (mx3.hub.org [206.223.169.73]) by mail.postgresql.org (Postfix) with ESMTP id 4389A632388 for ; Fri, 27 Mar 2009 06:48:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from serv2.oss.ntt.co.jp (serv2.oss.ntt.co.jp [222.151.198.100]) by mx3.hub.org (Postfix) with ESMTP id 233DF37C35A for ; Fri, 27 Mar 2009 06:48:04 -0300 (ADT) Received: from serv2.oss.ntt.co.jp (localhost [127.0.0.1]) by serv2.oss.ntt.co.jp (Postfix) with ESMTP id 53F3824810E; Fri, 27 Mar 2009 16:50:01 +0900 (JST) Received: from serv1.oss.ntt.co.jp (serv1.localdomain [172.19.0.2]) by serv2.oss.ntt.co.jp (Postfix) with ESMTP id 444062480C2; Fri, 27 Mar 2009 16:50:01 +0900 (JST) Received: from [127.0.0.1] (unknown [172.17.1.145]) by serv1.oss.ntt.co.jp (Postfix) with ESMTP id 165E2104165; Fri, 27 Mar 2009 16:50:01 +0900 (JST) Message-ID: <49CC8524.4090103@oss.ntt.co.jp> Date: Fri, 27 Mar 2009 16:49:56 +0900 From: Tatsuhito Kasahara User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Simon Riggs CC: pgsql-hackers@postgresql.org Subject: Re: display previous query string of idle-in-transaction 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> In-Reply-To: <1238139418.16568.555.camel@ebony.2ndQuadrant> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/1116 X-Sequence-Number: 135794 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. -- Tatsuhito Kasahara kasahara.tatsuhito@oss.ntt.co.jp