Re: pg_top

John R Pierce <pierce@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.)
        regards, tom lane