From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-patches@postgresql.org
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages
Date: Mon, 14 May 2007 09:52:30 -0400
Message-ID: <9814.1179150750@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.64.0705140926470.9478@westnet.com>
References: <461E108D.6080709@enterprisedb.com>
<Pine.GSO.4.64.0705121926420.9615@westnet.com>
<20070514174531.71E0.ITAGAKI.TAKAHIRO@oss.ntt.co.jp>
<Pine.GSO.4.64.0705140926470.9478@westnet.com>
Greg Smith <gsmith@gregsmith.com> writes:
> 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".
If you can write something like that, why do we need the parameter at all?
regards, tom lane
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: tgl@sss.pgh.pa.us, gsmith@gregsmith.com, pgsql-patches@postgresql.org
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages
In-Reply-To: <9814.1179150750@sss.pgh.pa.us>
* 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