On Thu, Dec 20, 2012 at 4:17 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > John R Pierce <pie...@hogranch.com> writes: >> /me tossed another mumbled curse at whomever changed that field name. > > The reason for the field name change was that the semantics of the field > changed. You typically ought to look at what the application is > actually doing with the field, not just do s/current_query/query/g > and expect that all will be well. (In particular, if the app is looking > for "idle" or "idle in transaction" state markers, it's going to need > more adjustment than that.)
IMSNHO, neither of these should have been changed, I would much rather have seen a new view or some other way of opting into the new functionality. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
