Re: Autovacuum versus rolled-back transactions - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Autovacuum versus rolled-back transactions
Date
Msg-id 20070601022108.GA7994@alvh.no-ip.org
Whole thread Raw
In response to Re: Autovacuum versus rolled-back transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Autovacuum versus rolled-back transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.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.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Autovacuum versus rolled-back transactions
Next
From: Tom Lane
Date:
Subject: Re: Autovacuum versus rolled-back transactions