Re: Dead Space Map for vacuum - Mailing list pgsql-hackers

From Jochem van Dieten
Subject Re: Dead Space Map for vacuum
Date
Msg-id f96a9b830612280124y2199acdcvf5a7fdb343bd4200@mail.gmail.com
Whole thread Raw
In response to Dead Space Map for vacuum  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Dead Space Map for vacuum  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
On 12/28/06, ITAGAKI Takahiro wrote:
>
> | [TODO item] Allow data to be pulled directly from indexes
> | Another idea is to maintain a bitmap of heap pages where all rows are
> | visible to all backends, and allow index lookups to reference that bitmap
> | to avoid heap lookups
>
> It is not done yet, but we can use DSM for this purpose. If the corresponding
> bit in DSM is '0', all tuples in the page are frozen and visible to all
> backends. We don't have to look up frozen pages only for visibiliby checking.

Does that really work in the absence of a retail index vacuum method?
What if the heap is already vacuumed, frozen and the bit for that page
in the DSM is set to '0', but the index still contains entries that
haven't been removed by a vacuum yet?

Jochem


pgsql-hackers by date:

Previous
From: Ron Mayer
Date:
Subject: Re: Load distributed checkpoint
Next
From: ITAGAKI Takahiro
Date:
Subject: Re: Dead Space Map for vacuum