Re: visibility maps and heap_prune - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: visibility maps and heap_prune
Date
Msg-id 4976041F.1070707@enterprisedb.com
Whole thread Raw
In response to Re: visibility maps and heap_prune  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian wrote:
> Pavan Deolasee wrote:
>> On Mon, Dec 8, 2008 at 11:33 AM, Pavan Deolasee <pavan.deolasee@gmail.com>wrote:
>>
>>>
>>> On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
>>> heikki.linnakangas@enterprisedb.com> wrote:
>>>
>>>> If you see a straightforward way, please submit a patch!
>>>>
>>>>
>>> Will do that.
>>>
>>>
>> Here is a patch which implements this. The PD_ALL_VISIBLE flag is set if all
>> tuples in the page are visible to all transactions and there are no DEAD
>> line pointers in the page. The second check is required so that VACUUM takes
>> up the page. We could slightly distinguish the two cases (one where the page
>> requires vacuuming only because of DEAD line pointers and the other where
>> the page-tuples do not require any visibility checks), but I thought its not
>> worth the complexity.
> 
> Is this patch for 8.4?

We already went through this:

http://archives.postgresql.org/message-id/496F6A8E.8020908@enterprisedb.com

I guess I'll follow Robert's advice and add this to the first 8.5 commit 
fest page.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: libpq WSACleanup is not needed
Next
From: Bruce Momjian
Date:
Subject: Re: Polymorphic types vs. domains