Received: from localhost (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 9ABF7633F07
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Tue, 28 Jul 2009 08:43:27 -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 41044-09
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Tue, 28 Jul 2009 11:43:10 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by mail.postgresql.org (Postfix) with SMTP id 8BD5263234F
	for <pgsql-hackers@postgresql.org>;
	Tue, 28 Jul 2009 08:43:16 -0300 (ADT)
Received: (qmail invoked by alias); 28 Jul 2009 11:43:14 -0000
Received: from fsgw.f-secure.com (EHLO fsopti579.localnet) [193.110.108.33]
	by mail.gmx.net (mp058) with SMTP; 28 Jul 2009 13:43:14 +0200
X-Authenticated: #495269
X-Provags-ID: V01U2FsdGVkX18hV0JD2c0hMxbOZwTnBr5y+LM3dyWswosEClOnrc
	ksrwmfe9KWlRMp
From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-hackers@postgresql.org
Subject: Re: display previous query string of idle-in-transaction
Date: Tue, 28 Jul 2009 14:43:10 +0300
User-Agent: KMail/1.11.2 (Linux/2.6.26-2-686; KDE/4.2.4; i686; ; )
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>,
	Kevin Grittner <Kevin.Grittner@wicourts.gov>, daveg <daveg@sonic.net>,
	Simon Riggs <simon@2ndquadrant.com>, decibel <decibel@decibel.org>,
	Greg Stark <stark@enterprisedb.com>, Asko Oja <ascoja@gmail.com>,
	Tatsuhito Kasahara <kasahara.tatsuhito@oss.ntt.co.jp>
References: <49C9F49B.8020003@oss.ntt.co.jp>
	<603c8f070907240758g34c1c54fp9a618e86adcc49a0@mail.gmail.com>
	<27627.1248448500@sss.pgh.pa.us>
In-Reply-To: <27627.1248448500@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907281443.10911.peter_e@gmx.net>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.73
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.066 tagged_above=-10 required=5 tests=AWL=0.066
X-Spam-Level: 
X-Archive-Number: 200907/1828
X-Sequence-Number: 142450

On Friday 24 July 2009 18:15:00 Tom Lane wrote:
> Another question is that this proposal effectively redefines the
> current_query column as not the "current" query, but something that
> might be better be described as "latest_query".  Should we change the
> name?  We'd probably break some client code if we did, but on the other
> hand the semantics change might break such code anyway.  Intentional
> breakage might not be such a bad thing if it forces people to take a
> fresh look at their code.

That breakage could be pretty widespread, though.  Maybe have current_query 
and last_query.