From: MichaelDBA <MichaelDBA@sqlexec.com>
To: Chris Hoover <chrish@aweber.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Evan Rempel <erempel@uvic.ca>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: New PG14 server won't start with >2GB shared_buffers
Date: Thu, 2 Mar 2023 16:56:44 -0500
Message-ID: <7647713c-7460-0753-d8ed-75806df6fbba@sqlexec.com> (raw)
In-Reply-To: <3FB541BC-E9CA-4F20-A2B6-05B902E6D98F@aweber.com>
References: <A446608A-42A3-4CBB-BD45-47BE009B0029@aweber.com>
<4b583c4a-022f-f452-c0c8-0a932a6ee411@gmail.com>
<C6285AA6-5195-4C8B-A599-401845EFD174@aweber.com>
<4a41387e-516e-0782-6110-89c05a99d020@sqlexec.com>
<20230225144930.GS9791@aart.rice.edu>
<B6A7F0D1-D06E-43F1-8787-BE90ADB3D05D@aweber.com>
<8b47c295-4b16-1a00-32e4-807103816475@uvic.ca>
<1177969.1677342917@sss.pgh.pa.us>
<F10C938D-C8CE-4BC9-BB41-770AEEDE5E4F@aweber.com>
<99663.1677457376@sss.pgh.pa.us>
<4AE75A90-7657-4A03-A2A7-C6B08247672E@aweber.com>
<3FB541BC-E9CA-4F20-A2B6-05B902E6D98F@aweber.com>
The default is 50, so somebody changed it?
Chris Hoover wrote on 3/2/2023 4:53 PM:
> Just to wrap this up, we finally found the issue.
>
> vm.overcommit_ratio was set to 0. After setting vm.overcommit_ratio
> to 50, the issue resolved.
>
> Thanks,
>
>
> Chris Hoover
> Senior DBA
> AWeber.com
> Cell: (803) 528-2269
> Email: chrish@aweber.com
>
>
>
>> On Feb 27, 2023, at 11:25 AM, Chris Hoover <chrish@aweber.com> wrote:
>>
>> Tom and everyone,
>>
>> We are leaning towards some sort of hardware/physical memory issue.
>> Our server admins are going to take the server and do some in depth
>> testing of the hardware.
>>
>> Thanks again for all the assistance over the weekend.
>>
>> Thanks,
>>
>>
>> Chris Hoover
>> Senior DBA
>> AWeber.com
>> Cell: (803) 528-2269
>> Email: chrish@aweber.com
>>
>>
>>
>>> On Feb 26, 2023, at 7:22 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>
>>> Chris Hoover <chrish@aweber.com> writes:
>>>> Got a chance to work on this today. Here is what I’m getting. I
>>>> used the same command that is used when the config has small memory.
>>>
>>> OK, so it still happens when interactive, which seems to exclude
>>> systemd.
>>>
>>> Have you tried setting huge_pages = off, as somebody suggested upthread?
>>> (The default setting of "try" ought to work anyway, but we've heard
>>> a few
>>> reports suggesting sometimes it doesn't.)
>>>
>>> Googling for ways to limit resources under Linux led me to mentions of
>>> /etc/security/limits.conf, which might be worth checking. The comments
>>> in that say it only applies to logins via PAM, which should include your
>>> interactive session and I'm not too sure about Patroni.
>>>
>>> Otherwise I'm kind of running out of ideas :-(. *Something* is clearly
>>> interfering with your resource limits, but I don't know what.
>>>
>>> regards, tom lane
>>
>
Regards,
Michael Vitale
Michaeldba@sqlexec.com <mailto:michaelvitale@sqlexec.com>
703-600-9343
Attachments:
[image/jpeg] pgadvanced3.jpg (20.6K, ../7647713c-7460-0753-d8ed-75806df6fbba@sqlexec.com/3-pgadvanced3.jpg)
download | view image
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: MichaelDBA@sqlexec.com, chrish@aweber.com, tgl@sss.pgh.pa.us, erempel@uvic.ca, pgsql-admin@lists.postgresql.org
Subject: Re: New PG14 server won't start with >2GB shared_buffers
In-Reply-To: <7647713c-7460-0753-d8ed-75806df6fbba@sqlexec.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox