From: Greg Smith <gsmith@gregsmith.com>
To: pgsql-patches@postgresql.org
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages
Date: Mon, 14 May 2007 09:34:21 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0705140926470.9478@westnet.com> (raw)
In-Reply-To: <20070514174531.71E0.ITAGAKI.TAKAHIRO@oss.ntt.co.jp>
References: <461E108D.6080709@enterprisedb.com>
<Pine.GSO.4.64.0705121926420.9615@westnet.com>
<20070514174531.71E0.ITAGAKI.TAKAHIRO@oss.ntt.co.jp>
On Mon, 14 May 2007, ITAGAKI Takahiro wrote:
> BTW, your patch will cut LRU writes short, but will not encourage to
> do more works. So should set more aggressive values to bgwriter_lru_percent
> and bgwriter_lru_maxpages as defaults?
Setting a bigger default maximum is one possibility I was thinking about.
Since the whole background writer setup is kind of complicated, the other
thing I was working on is writing a guide on how to use the new
pg_stat_bgwriter information to figure out if you need to increase
bgwriter_[all|lru]_pages (and the other parameters too). It makes it much
easier to write that if you can say "You can safely set
bgwriter_lru_maxpages high because it only writes what it needs to based
on your usage".
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmith@gregsmith.com, pgsql-patches@postgresql.org
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages
In-Reply-To: <Pine.GSO.4.64.0705140926470.9478@westnet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox