Re: Interesting glitch in autovacuum - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Interesting glitch in autovacuum
Date
Msg-id 20080910202733.GK4399@alvh.no-ip.org
Whole thread Raw
In response to Re: Interesting glitch in autovacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Interesting glitch in autovacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> Sorry, I got a bit confused there.  The vacuum's intentional pruning
> will use its own OldestXmin variable, which is known current at the
> start of the vacuum (and I think there were even proposals to advance
> it more frequently than that).  However, a vacuum could require some
> incidental system catalog fetches, which I think could result in
> prune operations based on RecentGlobalXmin on the catalog pages
> (cf index_getnext).

Hmm, right, and what Heikki said too.

> Anyway I think we are on the same page about the rest of the issues.
> Did you want to work on fixing them, or shall I?

Is this more or less what you had in mind?

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment

pgsql-hackers by date:

Previous
From: Tom Raney
Date:
Subject: Re: Planner question
Next
From: Simon Riggs
Date:
Subject: Re: Potential Join Performance Issue