Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Chris Hoover <chrish@aweber.com>
Mime-Version: 1.0 (1.0)
Subject: Re: New PG14 server won't start with >2GB shared_buffers
Date: Fri, 24 Feb 2023 22:29:47 -0500
Message-Id: <4D0088DC-C22D-4459-A793-72FC7402DC94@aweber.com>
References: <1088615.1677291592@sss.pgh.pa.us>
Cc: pgsql-admin@lists.postgresql.org
In-Reply-To: <1088615.1677291592@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4D0088DC-C22D-4459-A793-72FC7402DC94%40aweber.com>
Precedence: bulk

This is bare metal.

Thanks,

Chris Hoover=20

Sent from my iPhone

> On Feb 24, 2023, at 21:19, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> =EF=BB=BFChris Hoover <chrish@aweber.com> writes:
>> I have a new server that has 1TB ram (not a typo).  I have been fighting w=
ith this evening to start up with a shared_buffer setting over 2GB.  When th=
e memory allocation  breaks 2GB, the database won=E2=80=99t start.  I=E2=80=99=
ve dropped it down to 500M to get the database online.  We=E2=80=99ve tried b=
oth SysV memory and mmap memory.
>=20
> Are you running inside a VM, or cgroup, or something else that might
> be imposing a memory limit?
>=20
>            regards, tom lane