Re: Lock problem with autovacuum truncating heap

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Jan Wieck <JanWieck(at)yahoo(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lock problem with autovacuum truncating heap
Date: 2011-03-26 17:44:09
Message-ID: AANLkTi=GSe6CwLdgQ1MMscLShGL02TYVL2uaXhmsWsXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 27, 2011 at 01:12, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-26 17:51:21 Re: race condition in sync rep
Previous Message Martijn van Oosterhout 2011-03-26 17:16:34 Re: Open issues for collations