Re: [DOCS] bgwriter_lru_multiplier blurbs inconsistent - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [DOCS] bgwriter_lru_multiplier blurbs inconsistent
Date
Msg-id 11682.1200859720@sss.pgh.pa.us
Whole thread Raw
In response to bgwriter_lru_multiplier blurbs inconsistent  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> 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

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: bgwriter_lru_multiplier blurbs inconsistent
Next
From: David Fetter
Date:
Subject: Re: [GENERAL] SHA1 on postgres 8.3