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 CABOikdMrfTdP35cs_gZ-GfLxH2+qS9JJoWf7=PQo7pPBBqFeNw@mail.gmail.com
Whole thread Raw
In response to Re: Setting visibility map in VACUUM's second phase  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Setting visibility map in VACUUM's second phase
List pgsql-hackers
Hi Jeff,

On Thu, Jan 24, 2013 at 2:41 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
>
> lazy_vacuum_page now pins and unpins the vmbuffer for each page it marks
> all-visible, which seems like a lot of needless traffic since the next
> vmbuffer is likely to be the same as the previous one.
>

Good idea. Even though the cost of pinning/unpinning may not be high
with respect to the vacuum cost itself, but it seems to be a good idea
because we already do that at other places. Do you have any other
review comments on the patch or I'll fix this and send an updated
patch soon.

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



pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: CF3+4 (was Re: Parallel query execution)
Next
From: Xi Wang
Date:
Subject: [PATCH 0/3] Work around icc miscompilation