Skip site navigation (1) Skip section navigation (2)

Re: Fully replacing ps_status (was Re: [COMMITTERS] pgsql:

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fully replacing ps_status (was Re: [COMMITTERS] pgsql:
Date: 2006-06-27 22:44:46
Message-ID: 200606272244.k5RMikG14929@momjian.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Tom Lane wrote:
> momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> > Add GUC update_process_title to control whether 'ps' display is updated
> > for every command, default to on.
> 
> It strikes me that the ps_status support provides one important bit of
> information that is currently hard to get elsewhere; specifically, the
> "waiting" flag that gets added while blocked on a lock.  You can find
> out if a process is blocked by looking in pg_locks, but that's a fairly
> expensive probe in itself and then you have to join to pg_stat_activity
> to make any sense of it.  I wonder if we should add a "waiting" boolean
> column to pg_stat_activity?  Given the new implementation of
> pg_stat_activity, updating such a flag would be pretty cheap.

Nice idea.

-- 
  Bruce Momjian   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Mark KirkwoodDate: 2006-06-27 23:48:12
Subject: Re: Fully replacing ps_status (was Re: [COMMITTERS] pgsql:
Previous:From: Tom LaneDate: 2006-06-27 22:36:57
Subject: Fully replacing ps_status (was Re: [COMMITTERS] pgsql: Add GUC update_process_title to control whether 'ps' display is)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-06-27 23:25:28
Subject: pgsql: Remove embedded newline in string literal --- seems to make newer
Previous:From: Tom LaneDate: 2006-06-27 22:36:57
Subject: Fully replacing ps_status (was Re: [COMMITTERS] pgsql: Add GUC update_process_title to control whether 'ps' display is)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group