Skip site navigation (1) Skip section navigation (2)

Re: Dead Space Map for vacuum

From: "Jochem van Dieten" <jochemd(at)gmail(dot)com>
To: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Dead Space Map for vacuum
Date: 2006-12-28 09:24:51
Message-ID: f96a9b830612280124y2199acdcvf5a7fdb343bd4200@mail.gmail.com (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-hackers by date

Next:From: ITAGAKI TakahiroDate: 2006-12-28 09:26:37
Subject: Re: Dead Space Map for vacuum
Previous:From: Ron MayerDate: 2006-12-28 09:18:56
Subject: Re: Load distributed checkpoint

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group