public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: [email protected]
Cc: Hackers <[email protected]>
Subject: Re: bgwriter_lru_multiplier blurbs inconsistent
Date: Sun, 20 Jan 2008 15:08:40 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Alvaro Herrera <[email protected]> writes:
> Is the bgwriter_lru_multiplier parameter a limit on the number to scan
> or to write?  GUC and docs seem to contradict one another.  GUC says

> #: utils/misc/guc.c:1834
> #, fuzzy
> msgid "Background writer multiplier on average buffers to scan per round."

> The docs say
>          Unless limited by <varname>bgwriter_lru_maxpages</>, the number
>          of dirty buffers written in each round is determined by reference
>          to the number of new buffers that have been needed by server
>          processes during recent rounds.  This number is multiplied by
>          <varname>bgwriter_lru_multiplier</> to arrive at the estimate
>          of the number of buffers that will be needed during the next round.

> Which one is correct?  Do we need a correction of either?

We multiply the average number of new buffers used per round by the
multiplier, and use that as the target for the number of clean buffers
to have in front of the sweep hand.  Any of these that are dirty will
be written (until we exceed maxpages written).  So it's the number to scan.

I don't find either the docs or the msgid to be wrong, exactly; but if
you have a proposal for better wording, I'm all ears.

			regards, tom lane

view thread (7+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: bgwriter_lru_multiplier blurbs inconsistent
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox