From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: visibility maps and heap_prune |
Date: | 2008-12-08 12:56:49 |
Message-ID: | 2e78013d0812080456s2158fc9ex30f90250a3eadd5c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 8, 2008 at 11:33 AM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>wrote:
>
>
> On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
> heikki(dot)linnakangas(at)enterprisedb(dot)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.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
visibility_maps_prune.patch | text/x-patch | 7.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2008-12-08 13:01:02 | Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine |
Previous Message | Merlin Moncure | 2008-12-08 12:53:48 | Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine |