From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: david_sisson@dell.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date: Sat, 21 Jan 2023 18:33:03 -0500
Message-ID: <1113361.1674343983@sss.pgh.pa.us> (raw)
In-Reply-To: <20230121232922.juo7t3fhaso7qh3s@awork3.anarazel.de>
References: <17757-dbdfc1f1c954a6db@postgresql.org>
<4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com>
<20230121232922.juo7t3fhaso7qh3s@awork3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> On 2023-01-22 00:10:29 +0100, Tomas Vondra wrote:
>> I doubt we want to just go straight to changing the default value for
>> everyone. IMHO if the "try" logic is somehow broken, we should fix the
>> try logic, not mess with the defaults.
> Agreed. But we could disable huge pages explicitly inside initdb - there's
> really no point in using it there...
One of the things initdb is trying to do is establish a set of values
that is known to allow the server to start. Not using the same settings
that the server is expected to use would break that idea completely.
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, andres@anarazel.de, tomas.vondra@enterprisedb.com, david_sisson@dell.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
In-Reply-To: <1113361.1674343983@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