From: Tom Lane <tgl@sss.pgh.pa.us>
To: Siegfried Kiermayer <sicaine@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Segfault when running postgres inside kubernetes with huge pages
In-reply-to: 
 <CAC-et2dPHZkroNELgfVCS-NE7fD93jQiygoYAOOkmgJ+uc-ARA@mail.gmail.com>
References: 
 <CAC-et2dPHZkroNELgfVCS-NE7fD93jQiygoYAOOkmgJ+uc-ARA@mail.gmail.com>
Comments: In-reply-to Siegfried Kiermayer <sicaine@gmail.com>
	message dated "Tue, 07 Nov 2023 18:41:38 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <667005.1699455446.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 08 Nov 2023 09:57:26 -0500
Message-ID: <667006.1699455446@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/667006.1699455446%40sss.pgh.pa.us>
Precedence: bulk

Siegfried Kiermayer <sicaine@gmail.com> writes:
> we are using zalando postgres operator and i changed / set huge pages
> on kubernetes nodes from something undefined to 1536 (undefined
> because i was pretty sure before changing it to 1536 i saw an initial
> value of 1024 with 670 in use.

This previous discussion might hold the clue:

https://www.postgresql.org/message-id/CAFpoUr1ggmGs8qpoKvYxNBO3h-T-n%2BMNh=
%2BJnLRYsYhHurVOiGQ%40mail.gmail.com

> I would go into more detail but honestly I believe this might be easy
> to find and I also assume it shouldn't segfault but return an error
> message indicating the / a issue.

There is not that much we can do about operating system bugs.

			regards, tom lane