Re: pg_top

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John R Pierce <pierce(at)hogranch(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_top
Date: 2012-12-20 22:23:47
Message-ID: CAHyXU0yw=9d5qR4iiifoN3-jjGiFsc4SpmxkNR02nBYmuigfhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 20, 2012 at 4:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.)

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

In response to

Responses

  • Re: pg_top at 2012-12-21 07:02:11 from Brett Maton

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua Berkus 2012-12-20 22:28:43 Re: Cascading replication: should we detect/prevent cycles?
Previous Message Tom Lane 2012-12-20 22:17:25 Re: pg_top