Re: BufFreelistLock - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: BufFreelistLock
Date
Msg-id 1291988678-sup-5714@alvh.no-ip.org
Whole thread Raw
In response to Re: BufFreelistLock  (Jim Nasby <jim@nasby.net>)
Responses Re: BufFreelistLock  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
Excerpts from Jim Nasby's message of jue dic 09 16:54:24 -0300 2010:

> Ideally, the clock sweep would be run by bgwriter and not individual backends. In that case it shouldn't matter much
whatthe performance of the sweep is. To do that I think we'd want the bgwriter to target there being X number of
bufferson the free list instead of (or in addition to) targeting how many dirty buffers need to be written. This would
mirrorwhat operating systems do; they strive to keep X number of pages on the free list so that when a process needs
memoryit can get it quickly.
 

Isn't it what it does if you set bgwriter_lru_maxpages to some very
large value?

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: initdb failure with Postgres 8.4.4
Next
From: "BRUSSER Michael"
Date:
Subject: Re: initdb failure with Postgres 8.4.4