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

-----Original Message-----
From: Fan Liu
Sent: 2020年2月21日 10:15
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: RE: [Bus error] huge_pages default value (try) not fall back

-----Original Message-----
>From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
>Sent: 2020年2月19日 17:36
>To: Fan Liu <fan(dot)liu(at)ericsson(dot)com>
>Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
>Subject: Re: [Bus error] huge_pages default value (try) not fall back
>
>> 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.

-----------------------------------

Hi Dmitry,

I had try the workaround. The result is that there is still bus error, but postgresql did come up.

I am not that understand why this could happen.

Attached core dump file, could you take a look?

$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/lib/postgresql10/bin/postgres --boot -x0 -F -c max_connections=20 -c share', real uid: 26, effective uid: 26, real gid: 26, effective gid: 26, execfn: '/usr/lib/postgresql10/bin/postgres', platform: 'x86_64'

BRs,
Fan Liu