From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Chris Hoover <chrish(at)aweber(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: New PG14 server won't start with >2GB shared_buffers |
Date: | 2023-02-25 14:53:45 |
Message-ID: | a4638ea7-5e3f-a78b-8729-f440b52b0d54@sqlexec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I sincerely apologize. I should have read this stuff more closely.
Jeff Janes wrote on 2/25/2023 9:51 AM:
> On Sat, Feb 25, 2023 at 9:05 AM MichaelDBA <MichaelDBA(at)sqlexec(dot)com
> <mailto:MichaelDBA(at)sqlexec(dot)com>> wrote:
>
> I just don't get what all this fuss is about trying to get PG up
> on the smallest possible values for shared_buffers, especially
> considering this person has 1 TB of memory?
>
>
> The fuss is why he can't make it bigger. No one wants to make it as
> small as possible.
>
> Chris Hoover wrote on 2/25/2023 8:07 AM:
>>
>> Here is shmall:
>> kernel.shmall = 17179869184
>
>
> How did that get so small? On my Ubuntu18.04, it comes out of the box
> at 2^64 - 1. Why would anyone have set about making it smaller? Now
> the current value should still be big enough, but I wonder what else
> got changed while someone was monkeying with things that didn't need
> to be monkeyed with.
>
> Cheers,
>
> Jeff
Regards,
Michael Vitale
Michaeldba(at)sqlexec(dot)com <mailto:michaelvitale(at)sqlexec(dot)com>
703-600-9343
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Hoover | 2023-02-25 14:55:19 | Re: New PG14 server won't start with >2GB shared_buffers |
Previous Message | Jeff Janes | 2023-02-25 14:51:32 | Re: New PG14 server won't start with >2GB shared_buffers |