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
Date: Wed, 08 Nov 2023 09:57:26 -0500
Message-ID: <667006.1699455446@sss.pgh.pa.us> (raw)
In-Reply-To: <CAC-et2dPHZkroNELgfVCS-NE7fD93jQiygoYAOOkmgJ+uc-ARA@mail.gmail.com>
References: <CAC-et2dPHZkroNELgfVCS-NE7fD93jQiygoYAOOkmgJ+uc-ARA@mail.gmail.com>
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...> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, sicaine@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Segfault when running postgres inside kubernetes with huge pages
In-Reply-To: <667006.1699455446@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox