Re: Visibility map, partial vacuums - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Visibility map, partial vacuums
Date
Msg-id 4936884B.6050205@enterprisedb.com
Whole thread Raw
In response to Re: Visibility map, partial vacuums  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Visibility map, partial vacuums  (Gregory Stark <stark@enterprisedb.com>)
Re: Visibility map, partial vacuums  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Heikki Linnakangas wrote:
> Here's an updated version, with a lot of smaller cleanups, and using 
> relcache invalidation to notify other backends when the visibility map 
> fork is extended. I already committed the change to FSM to do the same. 
> I'm feeling quite satisfied to commit this patch early next week.

Committed.

I haven't done any doc changes for this yet. I think a short section in 
the "database internal storage" chapter is probably in order, and the 
fact that plain VACUUM skips pages should be mentioned somewhere. I'll 
skim through references to vacuum and see what needs to be changed.

Hmm. It just occurred to me that I think this circumvented the 
anti-wraparound vacuuming: a normal vacuum doesn't advance relfrozenxid 
anymore. We'll need to disable the skipping when autovacuum is triggered 
to prevent wraparound. VACUUM FREEZE does that already, but it's 
unnecessarily aggressive in freezing.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: ohp@pyrenet.fr
Date:
Subject: Re: cvs head initdb hangs on unixware
Next
From: Magnus Hagander
Date:
Subject: Re: Re: [BUGS] libpq does not manage SSL callbacks properly when other libraries are involved.