Skip site navigation (1) Skip section navigation (2)

Re: [Testperf-general] BufferSync and bgwriter

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Testperf-general] BufferSync and bgwriter
Date: 2004-12-17 18:13:13
Message-ID: 878y7wkd3a.fsf@stark.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Jan Wieck <JanWieck(at)yahoo(dot)com> writes:

> Doesn't cranking up the bgwriter_percent to 100 effectively make the entire
> shared memory a write-through cache? In other words, with 100% the bgwriter
> will allways write all dirty blocks out and it becomes unlikely to avoid an IO
> for subsequent modificaitons to the same data block.

If the goal is to not write out hot pages why look in T1 at all? Why not just
flush 100% of the dirty pages from T2 and ignore T1 entirely?

-- 
greg


In response to

pgsql-hackers by date

Next:From: Thomas HallgrenDate: 2004-12-17 19:12:30
Subject: Permissions within a function
Previous:From: Tom LaneDate: 2004-12-17 17:49:59
Subject: Re: Call for port reports

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group