Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id 966FB4764B9; Mon, 23 Sep 2002 10:50:05 -0400 (EDT)
Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251])
	by postgresql.org (Postfix) with ESMTP
	id 6E64D47649F; Mon, 23 Sep 2002 10:50:03 -0400 (EDT)
Received: (from pgman@localhost)
	by candle.pha.pa.us (8.11.6/8.10.1) id g8NEnrl11375;
	Mon, 23 Sep 2002 10:49:53 -0400 (EDT)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200209231449.g8NEnrl11375@candle.pha.pa.us>
Subject: Re: [SQL] Monitoring a Query
In-Reply-To: <3D8F25B6.3090809@MetroNY.com>
To: Aaron Held <aaron@MetroNY.com>
Date: Mon, 23 Sep 2002 10:49:53 -0400 (EDT)
Cc: Roberto Mello <rmello@cc.usu.edu>,
	Neil Conway <neilc@samurai.com>, pgsql-sql@postgresql.org,
	pgsql-general@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL99 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200209/997
X-Sequence-Number: 30578

Aaron Held wrote:
> It looks like that just timestamps things in its connection pool, that 
> is what I do now.
> 
> What I would like is to know about queries that have not finished yet.

OK, added to TODO:

	* Add start time to pg_stat_activity

Should we supply the current duration too?  That value would change on
each call.   Seems redundant.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073