Re: New PG14 server won't start with >2GB shared_buffers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Hoover <chrish(at)aweber(dot)com>
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 00:22:56
Message-ID: 99663.1677457376@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Hoover 2023-02-27 16:25:04 Re: New PG14 server won't start with >2GB shared_buffers
Previous Message Chris Hoover 2023-02-26 22:01:13 Re: New PG14 server won't start with >2GB shared_buffers