Re: [HACKERS] Time to up bgwriter_lru_maxpages?
От | Jim Nasby |
---|---|
Тема | Re: [HACKERS] Time to up bgwriter_lru_maxpages? |
Дата | |
Msg-id | 52b9b447-5139-1052-9246-3fb2f4a6ecf7@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Time to up bgwriter_lru_maxpages? (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] Time to up bgwriter_lru_maxpages?
|
Список | pgsql-hackers |
On 2/1/17 3:36 PM, Michael Paquier wrote: > On Thu, Feb 2, 2017 at 7:01 AM, Jim Nasby <Jim.Nasby@bluetreble.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)
В списке pgsql-hackers по дате отправления: