Re: Visibility map and freezing - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Visibility map and freezing
Date
Msg-id 1232474958.2327.200.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Visibility map and freezing  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Visibility map and freezing  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, 2009-01-20 at 11:03 +0200, Heikki Linnakangas wrote:
> > - Are there some conditions where whole-table-scanning vacuum is
> more
> >   effective than vacuums using visibility map? If so, we should
> switch
> >   to full-scan *automatically*, without relying on user
> configurations.
> 
> Hmm, the only downside I can see is that skipping a page here and
> there could defeat the OS read-ahead. Perhaps we should call 
> posix_fadvise(SEQUENTIAL) to compensate. Or, we could modify the logic
> to only skip pages when there's at least N consecutive pages that can
> be skipped.

I would rather we didn't skip any pages at all unless the gains are
significant. Skipping the odd page makes no difference from a
performance perspective but may have a robustness impact.

"Significant gains" should take into account the size of both heap and
indexes, and recognise that we still scan whole indexes in either case.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: [BUGS] BUG #4186: set lc_messages does not work
Next
From: Hiroshi Inoue
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.