Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > If we apply Heikki's idea of advancing OldestXmin, I think what we
> > should do is grab the value from pgstats when vacuum starts, and each
> > time we're going to advance OldestXmin, grab the value from pgstats
> > again; accumulate the differences from the various pgstat grabs.  At the
> > end we send the accumulated differences as the new dead tuple count.
> 
> Considering that each of those values will be up to half a second old,
> I can hardly think that this will accomplish anything except to
> introduce a great deal of noise ...

Normally, yes, but the values can be older if the vacuum_cost_delay is
large.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

• Re: Autovacuum versus rolled-back transactions at 2007-06-01 01:19:28 from Tom Lane

Responses

• Re: Autovacuum versus rolled-back transactions at 2007-06-01 03:22:40 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2007-06-01 03:19:18
	Subject: Re: Autovacuum versus rolled-back transactions
Previous:	From: Robert Treat	Date: 2007-06-01 02:08:01
	Subject: Re: table partitioning pl/pgsql helpers