bgwriter_lru_maxpages range in postgresql.conf

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: bgwriter_lru_maxpages range in postgresql.conf
Date: 2017-11-16 18:26:59
Message-ID: CAMkU=1zAETupZDfthHe8pvQqpZovq4ZgJ=GmWgK3oh6vP3PDBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(My earlier post has been stuck in infinite moderation due to the use of a
common 6 letter abbreviation for configuration, so I will try again without
it)

With v10, commit 14ca9abfbe4643408a, the upper limit on
bgwriter_lru_maxpages was changed from 1000 to INT_MAX / 2, but
the postgresql.conf.sample was not updated.

#bgwriter_lru_maxpages = 100 # 0-1000 max buffers written/round

I don't see any precedence for including INT_MAX-type limits in the sample
configuration file, so maybe something like this:?

#bgwriter_lru_maxpages = 100 # max buffers written/round, 0 to turn
off

Cheers,

Jeff

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-11-16 18:36:09 Re: Transaction control in procedures
Previous Message Andres Freund 2017-11-16 18:22:08 Re: Inlining functions with "expensive" parameters