Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pJOdb-00079s-Ai for pgsql-bugs@arkaria.postgresql.org; Sun, 22 Jan 2023 00:55:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pJOdY-0001aS-H2 for pgsql-bugs@arkaria.postgresql.org; Sun, 22 Jan 2023 00:55:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pJOdY-0001aI-7w for pgsql-bugs@lists.postgresql.org; Sun, 22 Jan 2023 00:55:08 +0000 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pJOdT-0007MM-Pd for pgsql-bugs@lists.postgresql.org; Sun, 22 Jan 2023 00:55:07 +0000 Received: by mail-wr1-x42a.google.com with SMTP id e3so7833696wru.13 for ; Sat, 21 Jan 2023 16:55:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=PLLjH3aS42Pj7aMPhPt7SD6f6TPy8astmB9JZw1bP8I=; b=OfD8kFt4BAFZClv6TNolKEVDbFHjPE592qIzyszaoWAWE+jqeLbHr17sAfrBYeNJ+8 7Swis32La7HOwxTA5XLACL/ss/PUjyxObWfgWG8ePGIlkaEQ07Z0egW/cml5RZRBysK5 WF9RlwbYXDjLB8t1rQt0V+uks8oN4/a477ZBZYmb1cfw/JcLZMq2Q/vC8Dt9oqTY9ZKG GC6etv58FDz8jbv6moNDh0K2tyLnBoRr+iqeC7035UiBRJxI+p/8f/LeRG4DmSdDP8mz 51xPLHpEDyGAJeVkEwSsROImwPg31GWONAO/7/7fKt6pHMJ6OJopqCT+WdhEKieP/LDp 4Lrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=PLLjH3aS42Pj7aMPhPt7SD6f6TPy8astmB9JZw1bP8I=; b=1RqLBtUBpFQ98vgQVN5kVikalGZ+On79+bl46uGPqPPb+O/ZnkOmQzeO76ys95hKOJ XpUbUvjfxftVwi3xSp3EZaOo8tPKpXZAFJOEQj0yutYEA7Y4F+Z/1TgnrWripWTKkzgv QBPBJRzo+xbETrRReIkHGIRK6uNjwIYPjRPLjWdVSY+V/CsVSRdm7zXGaO+VUb5IELcI WuQXP/zNPRdxbrb14mWC3lCN4suiAFHpwG2P6I8S/k84gEZHsd9spt8IXKmq9t27oUgL ym8hZEMfkjp8/5MlrtyQT40hvPLrtg+hu6dF8z4zJ3x1mpCwuJbFD1q2OhTTKl5PlxiY EeTQ== X-Gm-Message-State: AFqh2krKRnaofbp2CidnqwSQuiVPbsL/t8BE8cuS5YGPUTx4ZGmK7qXL N550ga6AC+rT0xWiimRDe+F6ekpdyeHtyG9/EI+Ushgny10t2w3z/gW4qaA5wz1S0d+0ecC4koO es78PQSxBCofp73N/9pycG6cPeW5F6cmcvTvbgV/ZX2tGiR6jdw0MUDreDS5XZxzYra8o6TF9WP k5mZ5KFtfMc5DHl0sglwQPtiC5q0ISP8h6hG/J+QZuI7JQLqCExy5SZrP/Wrsp+i2ircoPeAsEh SP0aS6VG7j8Y2lzff8+4LXGrMu0q7dT6VyIaM9tj3i4glya X-Google-Smtp-Source: AMrXdXt0K7aiky+Z8IiH4RLO5yZO/q2Dy58dtklS/DTh9ZJJ5GnZptG9xUBrZS3PtPQYuWaFFXUpvA== X-Received: by 2002:adf:a147:0:b0:2be:34fb:673 with SMTP id r7-20020adfa147000000b002be34fb0673mr10919259wrr.52.1674348902111; Sat, 21 Jan 2023 16:55:02 -0800 (PST) Received: from [10.137.0.17] (ip-86-49-228-162.bb.vodafone.cz. [86.49.228.162]) by smtp.gmail.com with ESMTPSA id q17-20020a056000137100b002be4ff0c917sm5350584wrz.84.2023.01.21.16.55.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 21 Jan 2023 16:55:01 -0800 (PST) Message-ID: <127328f2-4e01-e9ec-c9b1-76aef967343f@enterprisedb.com> Date: Sun, 22 Jan 2023 01:55:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes Content-Language: en-US To: Tom Lane Cc: david_sisson@dell.com, pgsql-bugs@lists.postgresql.org References: <17757-dbdfc1f1c954a6db@postgresql.org> <4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com> <1113115.1674343827@sss.pgh.pa.us> From: Tomas Vondra In-Reply-To: <1113115.1674343827@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/22/23 00:30, Tom Lane wrote: > Tomas Vondra writes: >> On 1/20/23 23:48, PG Bug reporting form wrote: >>> Here is a PR with a possible fix: >>> https://github.com/postgres/postgres/pull/114/files > >> I doubt we want to just go straight to changing the default value for >> everyone. > > Yeah, that proposal is a non-starter. I could see providing an > initdb option to adjust the value applied during initdb, though. > > Ideally, maybe what we want is a generalized switch that could > replace any variable in the sample config, along the lines of > the server's "-c foo=bar". I recall having tried to do that and > having run into quoting hazards, but I did not try very hard. > Yeah, I was looking for something like "-c" in initdb, only to realize there's nothing like that. The main "problem" with adding that is that we're unlikely to backpatch that (I guess), and thus it does not really solve the issue for the OP. I'm not sure we'd be keen to backpatch a change of the default, but maybe we would ... regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company