Re: [Bus error] huge_pages default value (try) not fall back

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Fan Liu <fan(dot)liu(at)ericsson(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: [Bus error] huge_pages default value (try) not fall back
Date: 2020-02-19 09:35:50
Message-ID: 20200219093550.bhuchrxiyovo4i3j@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Panchal, Hiren (GE Corporate, consultant) 2020-02-19 09:44:27 Regarding postgres driver odbc issue
Previous Message Frank Heikens 2020-02-19 09:07:34 Re: [Bug Report] Week Day