Re: New PG14 server won't start with >2GB shared_buffers - Mailing list pgsql-admin

From Chris Hoover
Subject Re: New PG14 server won't start with >2GB shared_buffers
Date
Msg-id 4AE75A90-7657-4A03-A2A7-C6B08247672E@aweber.com
Whole thread Raw
In response to Re: New PG14 server won't start with >2GB shared_buffers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: New PG14 server won't start with >2GB shared_buffers  (Chris Hoover <chrish@aweber.com>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: New PG14 server won't start with >2GB shared_buffers
Next
From: Teju Jakkidi vlogs
Date:
Subject: Query taking long with levenshtein function