Horton

Re: Time to up bgwriter_lru_maxpages?

Jim Nasby <jim.nasby@bluetreble.com>

View thread View on postgr.es
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: "Joshua D. Drake" <jd@commandprompt.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-01-31T22:07:12Z
Lists: pgsql-hackers

Attachments

On 11/29/16 9:58 AM, Jeff Janes wrote:
>
>         Considering a single SSD can do 70% of that limit, I would say yes.
>
>
>     Next question becomes... should there even be an upper limit?
>
>
> Where the contortions needed to prevent calculation overflow become
> annoying?
>
> I'm not a big fan of nannyism in general, but the limits on this
> parameter seem particularly pointless.  You can't write out more buffers
> than exist in the dirty state, nor more than implied
> by bgwriter_lru_multiplier.  So what is really the worse that can happen
> if you make it too high?

Attached is a patch that ups the limit to INT_MAX / 2, which is the same 
as shared_buffers.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

Commits

  1. Increase upper bound for bgwriter_lru_maxpages.