From: | Chris Hoover <chrish(at)aweber(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Evan Rempel <erempel(at)uvic(dot)ca>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: New PG14 server won't start with >2GB shared_buffers |
Date: | 2023-02-27 16:25:04 |
Message-ID: | 4AE75A90-7657-4A03-A2A7-C6B08247672E@aweber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)aweber(dot)com
> On Feb 26, 2023, at 7:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Chris Hoover <chrish(at)aweber(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Teju Jakkidi vlogs | 2023-02-28 23:11:55 | Query taking long with levenshtein function |
Previous Message | Tom Lane | 2023-02-27 00:22:56 | Re: New PG14 server won't start with >2GB shared_buffers |