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

From Tom Lane
Subject Re: Visibility map, partial vacuums
Date
Msg-id 18941.1225199290@sss.pgh.pa.us
Whole thread Raw
In response to Re: Visibility map, partial vacuums  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Visibility map, partial vacuums
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> ... I'm not sure if it would 
> be safe to set the PD_ALL_VISIBLE_FLAG while holding just a shared lock, 
> though. If it is, then we could do just that.

Seems like it must be safe.  If you have shared lock on a page then no
one else could be modifying the page in a way that would falsify
PD_ALL_VISIBLE.  You might have several processes concurrently try to
set the bit but that is safe (same situation as for hint bits).

The harder part is propagating the bit to the visibility map, but I
gather you intend to only allow VACUUM to do that?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Visibility map, partial vacuums
Next
From: Tom Lane
Date:
Subject: Re: WIP patch: convert SQL-language functions to return tuplestores