Re: crash-safe visibility map, take three - Mailing list pgsql-hackers

From Robert Haas
Subject Re: crash-safe visibility map, take three
Date
Msg-id AANLkTi=K=26Nkx48H9nmUcmJNcuWhL60VqCy8OXCRr28@mail.gmail.com
Whole thread Raw
In response to Re: crash-safe visibility map, take three  (Jesper Krogh <jesper@krogh.cc>)
Responses Re: crash-safe visibility map, take three  (Jesper Krogh <jesper@krogh.cc>)
Re: crash-safe visibility map, take three  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
On Wed, Jan 5, 2011 at 3:22 PM, Jesper Krogh <jesper@krogh.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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: making an unlogged table logged
Next
From: Robert Haas
Date:
Subject: Re: What is lo_insert?