On Jan 5, 2011, at 8:10 PM, Robert Haas wrote:
> On Wed, Jan 5, 2011 at 3:22 PM, Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
>> Given a crash-safe visibility map, what purpuse does the PD_ALL_VISIBLE bit
>> serve?
> 
> If we modify a page on which PD_ALL_VISIBLE isn't set, we don't
> attempt to update the visibility map.  In theory, this is an important
> optimization to reduce contention on the visibility map page, since
> there are something like 64K heap pages per visibility map page.  In
> practice, I'm not sure in what workloads it matters or by how much.

What specific locking are you worried about? The page locks themselves? Isn't changing the bit essentially a single instruction operation?

This is sounding like premature optimization... ;)
--
Jim C. Nasby, Database Architect                   jim(at)nasby(dot)net
512.569.9461 (cell)                         http://jim.nasby.net

In response to

• Re: crash-safe visibility map, take three at 2011-01-06 02:10:15 from Robert Haas

Responses

• Re: crash-safe visibility map, take three at 2011-01-08 02:59:36 from Robert Haas

pgsql-hackers by date

Next:	From: Stephen Frost	Date: 2011-01-07 18:29:52
	Subject: Re: DISCARD ALL ; stored procedures
Previous:	From: Joel Jacobson	Date: 2011-01-07 18:10:34
	Subject: obj_unique_identifier(oid)