Re: pg_top

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_top
Date: 2012-12-20 22:17:25
Message-ID: 25451.1356041845@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

John R Pierce <pierce(at)hogranch(dot)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

In response to

  • Re: pg_top at 2012-12-20 18:18:34 from John R Pierce

Responses

  • Re: pg_top at 2012-12-20 22:23:47 from Merlin Moncure

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2012-12-20 22:23:47 Re: pg_top
Previous Message Joshua Berkus 2012-12-20 22:12:45 Re: Switching timeline over streaming replication