Re: [HACKERS] Time to up bgwriter_lru_maxpages? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Time to up bgwriter_lru_maxpages?
Date
Msg-id 20170202002740.rtvcrteryelvhvhj@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Time to up bgwriter_lru_maxpages?  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Time to up bgwriter_lru_maxpages?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 2017-02-02 09:22:46 +0900, Michael Paquier wrote:
> On Thu, Feb 2, 2017 at 9:17 AM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> > 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.
> 
> Time for int64 GUCs?

I don't think the GUC bit is the hard part.  We'd possibly need some
trickery (like not storing bufferid in BufferDesc anymore) to avoid
increasing memory usage.

- Andres



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Time to up bgwriter_lru_maxpages?
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Time to up bgwriter_lru_maxpages?