From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: [COMMITTERS] pgsql: Make large sequential scans and VACUUMs work in a limited-size |
Date: | 2007-05-30 21:09:55 |
Message-ID: | 20070530210955.GM7128@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Log Message:
> -----------
> Make large sequential scans and VACUUMs work in a limited-size "ring" of
> buffers, rather than blowing out the whole shared-buffer arena. Aside from
> avoiding cache spoliation, this fixes the problem that VACUUM formerly tended
> to cause a WAL flush for every page it modified, because we had it hacked to
> use only a single buffer. Those flushes will now occur only once per
> ring-ful. The exact ring size, and the threshold for seqscans to switch into
> the ring usage pattern, remain under debate; but the infrastructure seems
> done. The key bit of infrastructure is a new optional BufferAccessStrategy
> object that can be passed to ReadBuffer operations; this replaces the former
> StrategyHintVacuum API.
I think now is time to re-test the patch for advancing OldestXmin during
vacuum?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2007-05-31 07:36:13 | pgsql: Downgrade some low-level startup messages to DEBUG1. |
Previous Message | Tom Lane | 2007-05-30 21:02:02 | pgsql: Fix overly-strict sanity check in BeginInternalSubTransaction |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-30 22:00:20 | Re: New cast between inet/cidr and bytea |
Previous Message | Tom Lane | 2007-05-30 20:27:40 | Re: Ye olde drop-the-database-you-just-left problem |