Re: visibility maps and heap_prune

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: visibility maps and heap_prune
Date: 2010-02-26 02:49:10
Message-ID: 201002260249.o1Q2nAB04502@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Whatever happened to this? It was in the first 9.0 commitfest but was
returned with feedback but never updated:

https://commitfest.postgresql.org/action/patch_view?id=75

---------------------------------------------------------------------------

Pavan Deolasee wrote:
> ISTM that the PD_ALL_VISIBLE flag and the visibility map bit can be set at
> the end of pruning operation if we know that there are only tuples visible
> to all transactions left in the page. The way pruning is done, I think it
> would be straight forward to get this information.
>
> Thanks,
> Pavan
>
> --
> Pavan Deolasee
> EnterpriseDB http://www.enterprisedb.com

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-02-26 03:06:06 Re: Why isn't stats_temp_directory automatically created?
Previous Message Jeroen Vermeulen 2010-02-26 02:48:05 Re: Avoiding bad prepared-statement plans.