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 what the performance of the > sweep is. To do that I think we'd want the bgwriter to target there being X > number of buffers on the free list instead of (or in addition to) targeting > how many dirty buffers need to be written. This would mirror what operating > systems do; they strive to keep X number of pages on the free list so that > when a process needs memory it can get it quickly.
Isn't it what it does if you set bgwriter_lru_maxpages to some very large value? -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
