From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-hackers@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: daveg <daveg@sonic.net>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: decibel <decibel@decibel.org>
Cc: Greg Stark <stark@enterprisedb.com>
Cc: Asko Oja <ascoja@gmail.com>
Cc: Tatsuhito Kasahara <kasahara.tatsuhito@oss.ntt.co.jp>
Subject: Re: display previous query string of idle-in-transaction
Date: Tue, 28 Jul 2009 14:43:10 +0300
Message-ID: <200907281443.10911.peter_e@gmx.net> (raw)
In-Reply-To: <27627.1248448500@sss.pgh.pa.us>
References: <49C9F49B.8020003@oss.ntt.co.jp>
<603c8f070907240758g34c1c54fp9a618e86adcc49a0@mail.gmail.com>
<27627.1248448500@sss.pgh.pa.us>
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.
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: peter_e@gmx.net, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, Kevin.Grittner@wicourts.gov, daveg@sonic.net, simon@2ndquadrant.com, decibel@decibel.org, stark@enterprisedb.com, ascoja@gmail.com, kasahara.tatsuhito@oss.ntt.co.jp
Subject: Re: display previous query string of idle-in-transaction
In-Reply-To: <200907281443.10911.peter_e@gmx.net>
* 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