Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j4LlD-0005cC-Ma for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Feb 2020 09:35:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j4LlA-0002ij-Aq for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Feb 2020 09:35:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from <9erthalion6@gmail.com>) id 1j4Ll9-0002ic-Tc for pgsql-bugs@lists.postgresql.org; Wed, 19 Feb 2020 09:35:12 +0000 Received: from mail-wm1-x32f.google.com ([2a00:1450:4864:20::32f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <9erthalion6@gmail.com>) id 1j4Ll3-0001O0-9X for pgsql-bugs@lists.postgresql.org; Wed, 19 Feb 2020 09:35:10 +0000 Received: by mail-wm1-x32f.google.com with SMTP id t23so5699140wmi.1 for ; Wed, 19 Feb 2020 01:35:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=9qZBypOeJqKPXisNcW8XS+fies2DUPriwSSNcTbHB3I=; b=WLpCLhxWlnHjDjwNrHTqp7aQVW7QzlZ4e7H2dxydsaCWx/FazFOba6t3P3kmJ4e+ef /X1Stud2nAfa0DsUfoidj+ZhyVFJZrHDDo3cJ3lmM7sOV6dGYCROPTCQqsuuzq5Ajcbp qh/f5ctm6e0CtbFxgo5RISIds9MfGYD1VMgm9R4RTtISWVcXyJ6qUf7B1Mb7t5zHXJrT qACPgp2kyeulYKo7R7O16LXkSkCRggCkjXiw+6czHVbkF23nTVoYm1HBvnV6nJoHMlB0 OBBWGl68lw4h4x2UrO6c0I+b3FPUw9pB3K/jwR/zUTRePCBCvFp7iLUCCaX95H1ce6/k SpuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=9qZBypOeJqKPXisNcW8XS+fies2DUPriwSSNcTbHB3I=; b=qcknBweOWHO3Ms9rwJ24sIgebXKr4IfcpFy8S/DOEV6+Mh6LpJXxJIcsUnnec/wXs4 Jiblz94yy8Y2Ti4fD/OdxJt1qiBPRD0anaQfehNbv0g4RlgzUD33mCcBCAIvNHU7R0xS s6PX5nBPa3qdq7bI27axB041f1MnGf8btT5Ig8NvP2p9MteJ1+QNRgT+vBD7Oe1GQhHE QA9WgsiiS9z82xwPTVgE0u1u+du210x35+KIX4l6ytbNpJtblvDDvZg1ARSa6fMaD620 MiLUAaxaudyrMDAsWyg0wXvCKo+OMa7F6sN18swUoJXyZAxR7yNhYm+MRSOa/t+L3u0F WCBg== X-Gm-Message-State: APjAAAWDv481zACZZatTxP5vaR0igGxQ2m+F6tbEc5CyRJJ2ZcuZ78Nw zf2KfXtFclA03YZ3gfjHjVE= X-Google-Smtp-Source: APXvYqw1eAcnFTOFy1BHSmbSkQvz31r63D1EXNOVolclSGmaqgaKfXt9kisFv2q09nDdaCgN1oQLag== X-Received: by 2002:a05:600c:20c6:: with SMTP id y6mr8922893wmm.95.1582104903797; Wed, 19 Feb 2020 01:35:03 -0800 (PST) Received: from localhost ([185.85.220.200]) by smtp.gmail.com with ESMTPSA id z21sm2198245wml.5.2020.02.19.01.35.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Feb 2020 01:35:03 -0800 (PST) Date: Wed, 19 Feb 2020 10:35:50 +0100 From: Dmitry Dolgov <9erthalion6@gmail.com> To: Fan Liu Cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: [Bus error] huge_pages default value (try) not fall back Message-ID: <20200219093550.bhuchrxiyovo4i3j@localhost> References: <20200218093240.jd3lgoxmisyl2tt5@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Tue, Feb 18, 2020 at 12:31:51PM +0000, Fan Liu wrote: > > "Modify the docker image to be able to set huge_pages = off in /usr/share/postgresql/postgresql.conf.sample before initdb was ran (this is what I did)." > > I am working on this workaround , but has not really tested yet. So, do you think this could avoid this issue? Or do you see any side impact for this workaround? If you don't necessarily need to use huge pages, then yes, I guess it should work. In case if initdb tries to read config from some other location, you can always point it to whatever you need via -L option.