Re: Setting visibility map in VACUUM's second phase - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Setting visibility map in VACUUM's second phase
Date
Msg-id CABOikdNnhhpG-fM_g9+2o+m4jKJ_WD00Oyhi5yWkYye4-UGUgg@mail.gmail.com
Whole thread Raw
In response to Re: Setting visibility map in VACUUM's second phase  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Setting visibility map in VACUUM's second phase  (Pavan Deolasee <pavan.deolasee@gmail.com>)
List pgsql-hackers
On Thu, Dec 6, 2012 at 11:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>
> I think taking a second whack at setting the visibility bit is a fine
> idea, but let's drop all the rest of this premature optimization.
>

Fair enough. I thought about doing it that way but was worried that an
additional page scan will raise eyebrows. While it does not affect the
common case because we would have done that scan anyways in the
subsequent vacuum, but in the worst case where most of the pages not
remain all-visible by the time we come back to the second phase of
vacuum, this additional line pointer scan will add some overhead. With
couple of pluses for the approach, I won't mind doing it this way
though.

Thanks,
Pavan

-- 
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee



pgsql-hackers by date:

Previous
From: "David Rowley"
Date:
Subject: Re: Functional dependency in GROUP BY through JOINs
Next
From: Phil Sorber
Date:
Subject: Re: [WIP] pg_ping utility