Re: Time to up bgwriter_lru_maxpages?

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Time to up bgwriter_lru_maxpages?
Date: 2017-02-02 00:17:46
Message-ID: 52b9b447-5139-1052-9246-3fb2f4a6ecf7@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/1/17 3:36 PM, Michael Paquier wrote:
> On Thu, Feb 2, 2017 at 7:01 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> On 2/1/17 10:27 AM, Robert Haas wrote:
>>> This looks fine to me.
> This could go without the comments, they are likely going to be
> forgotten if any updates happen in the future.

I'm confused... I put the comments in there so if max shared buffers
ever changed the other one would hopefully be updated as well.

Speaking of which... I have a meeting in 15 minutes to discuss moving to
a server with 4TB of memory. With current limits shared buffers maxes at
16TB, which isn't all that far in the future. While 16TB of shared
buffers might not be a good idea, it's not going to be terribly long
before we start getting questions about it.
--
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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-02-02 00:22:46 Re: Time to up bgwriter_lru_maxpages?
Previous Message Michael Paquier 2017-02-01 23:46:11 Re: Cannot shutdown subscriber after DROP SUBSCRIPTION