Re: Lock problem with autovacuum truncating heap - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: Lock problem with autovacuum truncating heap
Date
Msg-id AANLkTi=GSe6CwLdgQ1MMscLShGL02TYVL2uaXhmsWsXQ@mail.gmail.com
Whole thread Raw
In response to Re: Lock problem with autovacuum truncating heap  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Lock problem with autovacuum truncating heap
List pgsql-hackers
On Sun, Mar 27, 2011 at 01:12, Simon Riggs <simon@2ndquadrant.com> wrote:
>> At the same time I would
>> change count_nondeletable_pages() so that it uses a forward scan direction
>> (if that leads to a speedup).

+1.

> Do we need that? Linux readahead works in both directions doesn't it?
> Guess it wouldn't hurt too much.

Yes, probably. AFAIK, RHEL 5 cannot readahead in backward scans.
It might be improved in the latest kernel, but it would be safe
not to rely on kernels except simple forward scans.

-- 
Itagaki Takahiro


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Open issues for collations
Next
From: Robert Haas
Date:
Subject: Re: race condition in sync rep