Re: pg_top - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_top
Date
Msg-id 25451.1356041845@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_top  (John R Pierce <pierce@hogranch.com>)
Responses Re: pg_top
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Joshua Berkus
Date:
Subject: Re: Switching timeline over streaming replication
Next
From: Merlin Moncure
Date:
Subject: Re: pg_top