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

Re: Autovacuum vacuums not setting start time in pg_stat_activity

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jim Nasby <jim(dot)nasby(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Autovacuum vacuums not setting start time in pg_stat_activity
Date: 2007-06-12 21:46:22
Message-ID: 20070612214622.GD8537@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> "Jim Nasby" <jim(dot)nasby(at)enterprisedb(dot)com> writes:
> > This is on a 8.2.3 database; vacuums started by autovacuum don't get  
> > their query_start time set.
> 
> Hmm.  Query_start is actually defined as "time of last client command
> receipt", so it's null just like client_addr/port are.  Not sure if
> there's anything we should put there that's more meaningful than the
> backend start time.

Let's put the current command (vacuum/analyze) start time in there.
Backend start time, I assume, is the time at which the current autovac
iteration was started.

Should this be backpatched if changed in 8.3?

-- 
Alvaro Herrera                          Developer, http://www.PostgreSQL.org/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-06-12 21:51:06
Subject: Re: Autovacuum vacuums not setting start time in pg_stat_activity
Previous:From: Tom LaneDate: 2007-06-12 21:14:49
Subject: Re: Autovacuum vacuums not setting start time in pg_stat_activity

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