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 1pZRJo-0007lZ-Ky for pgsql-general@arkaria.postgresql.org; Tue, 07 Mar 2023 07:01:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pZRJn-0005LI-4M for pgsql-general@arkaria.postgresql.org; Tue, 07 Mar 2023 07:01:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pZRJm-0005L9-Pv for pgsql-general@lists.postgresql.org; Tue, 07 Mar 2023 07:01:02 +0000 Received: from mail-pj1-x1032.google.com ([2607:f8b0:4864:20::1032]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pZRJe-0001Nt-Du for pgsql-general@postgresql.org; Tue, 07 Mar 2023 07:00:55 +0000 Received: by mail-pj1-x1032.google.com with SMTP id kb15so12314376pjb.1 for ; Mon, 06 Mar 2023 23:00:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678172453; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=mxP3+AkjqxPSvA/YK8YhczQsfXmqeej1j8Vmad9lbjg=; b=TqZJhn3dlKCVCO2xTjicBAp58JZhjgMUhWFtFCJ448M2DEqF1qoEzCo6+8bbTH8aHL RzJaNW3F9Zoo/AJS9N6AjbL//DHgKvCHvnwVIyGKzjfpNjgMbQIcU+rXiv7KEzxL5PJ7 qfZjbUdjkppWKvsLf9dFtG2XZVOJUXSWxjOREbKbUXE+eowel3TsGh1FBZatXhhtHTK9 1Z32uwLfLycxTQ+7lu9k4uummAgghsH+UdU4eoxLyilfMC58HVWNpNL6ExG1oKde8Wje GXRRecpPwlBXJVWoSCMQY8fncE5nZNLBtYmvsURJDZ7s9/dEH5SeIzfHbRNJZcBIP+OL Yvkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678172453; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mxP3+AkjqxPSvA/YK8YhczQsfXmqeej1j8Vmad9lbjg=; b=vVp7U05/a2m2MkKVl0WWT0ndgIVk/q8EIgT/KyozYUhl4Klm8kQtj+Vqhu/HThicqY UNuzeYqVUIEHMONicxNS9/w6SKFRmPB/QNlQj/J6kwig+EAKuSgoCwepxCt5rqvuHpVC xn/zedh6WJ+7P7/F+MV4BXjYwpi44CxkHJk1a/el4RX736ceXfoCgLLj8H5eNpbgLfFu LEQ0eSOYcKt45O8ZlSdE/DpVr4+SiblEVyGZyo3Wk0AoNDki6YodJBbCBKxwz1oIACLK ZSc7WgJTz5jQTJs6CQjjtbMMG4+84L2hAuJd6XF+VbxvwosyoAQb57VvHCGeGglGVgXb q5vg== X-Gm-Message-State: AO0yUKVSTRNYlT2gdGArDhsbC2GGfU6L+l9uEIZSh3yB7oRl7iDET9WN RVG4u7oMPASxhI2ZqpZlmFU= X-Google-Smtp-Source: AK7set9Jqc0bb/J93+e+ZSgXKfdu8fXjaqYnNx6NwMJT//U+jtzaaDL8fL5tnaLdM5yTu5sB3EXcig== X-Received: by 2002:a17:90b:3841:b0:237:461c:b31a with SMTP id nl1-20020a17090b384100b00237461cb31amr14428744pjb.32.1678172453507; Mon, 06 Mar 2023 23:00:53 -0800 (PST) Received: from jrouhaud (2001-b011-1006-937a-f1c6-c856-8731-0a63.dynamic-ip6.hinet.net. [2001:b011:1006:937a:f1c6:c856:8731:a63]) by smtp.gmail.com with ESMTPSA id j14-20020a17090a2a8e00b0023739b104f8sm6800873pjd.50.2023.03.06.23.00.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Mar 2023 23:00:52 -0800 (PST) Date: Tue, 7 Mar 2023 15:00:50 +0800 From: Julien Rouhaud To: M Tarkeshwar Rao Cc: "pgsql-general@postgresql.org" Subject: Re: Multiple core dump errors are thrown by initdb =?utf-8?Q?when?= =?utf-8?Q?_Huge_pages_are_enabled_in_OS_and_huge=5Fpages_is_set_to_?= =?utf-8?B?4oCcb2Zm4oCd?= in postgresql.conf.sample in Kubernetes. Message-ID: <20230307070050.dike2ll277yf56h2@jrouhaud> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Tue, Mar 07, 2023 at 05:44:53AM +0000, M Tarkeshwar Rao wrote: > > We are facing following issue with postgres db with Kubernetes. Is huge pages > not supported in Kubernetes environment? > Multiple core dump errors are thrown by initdb when Huge pages are enabled in > OS and huge_pages is set to “off” in postgresql.conf.sample in Kubernetes. > In this case, the initdb utility exists with code, success message is also > printed in its logs and DB server is started successfully. > > Queries: > How can this issue be fixed? > If no, can these errors be ignored or is there any repercussion of these > errors, since DB is initialized & started successfully. > > NOTE: If we do not set huge_pages to “off”, and use its default value, then > db is also not starting. FTR this has already been reported a few weeks ago, see https://www.postgresql.org/message-id/flat/17757-dbdfc1f1c954a6db%40postgresql.org. You can also look at https://commitfest.postgresql.org/42/4143/ (and maybe test) as a possible fix that could be backpatched to released versions.