Re: BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: i(at)avdd(dot)co
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily
Date: 2012-08-30 13:38:02
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

On Thu, Aug 30, 2012 at 04:34:18AM +0000, i(at)avdd(dot)co wrote:
> The following bug has been logged on the website:
> Bug reference: 7511
> Logged by: Adrian Dries
> Email address: i(at)avdd(dot)co
> PostgreSQL version: Unsupported/Unknown
> Operating system: any
> Description:
> In trying 9.2 I find pg_stat_activity.procpid has been renamed to pid.
> It seems the premise of this is
> If we're going to rename current_query to query--what Scott's patch does
> here--that will force all code using pg_stat_activity to be rewritten. This
> seems like the perfect time to also change "procpid" to "pid", finally blow
> away that wart.
> A premise that is untrue: changing a subset of columns on a relation does
> not force "all code" using that relation to be rewritten:
> SELECT procpid FROM pg_stat_activity WHERE procpid <> pg_backend_pid()

True. We were thinking more of tools that display all pg_stat_activity

Bruce Momjian <bruce(at)momjian(dot)us>

+ It's impossible for everything to be true. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message MirrorX 2012-08-30 14:37:44 Re: hot standby lagging vs warm that is up-to-date
Previous Message Tom Lane 2012-08-30 13:37:26 Re: BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily