Reply-To: mjoigny@neteven.com
Subject: Re: PG 11.8 > PG 12.3 : Unable to allocate section memory
To: MichaelDBA <MichaelDBA@sqlexec.com>, tgl@sss.pgh.pa.us
Cc: pgsql-admin@postgresql.org
References: <64eae88b-8ac5-366c-b6a2-e7b59b3d191b@neteven.com>
 <544598c0-8d92-b66b-e015-4fc7e5735c35@sqlexec.com>
From: "JOIGNY Michael @Neteven" <mjoigny@neteven.com>
Message-ID: <1d659a5c-9b10-c92a-c901-e61aa1a0bcdc@neteven.com>
Date: Wed, 12 Aug 2020 16:54:07 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <544598c0-8d92-b66b-e015-4fc7e5735c35@sqlexec.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

Hi Michael, Tom,

Thanks for your help.

Le 12/08/2020 à 16:26, MichaelDBA a écrit :
> Please specify some other stuff:
>
> 1. PG onprem or cloud? If cloud, which one and what instance type.
Onprem
> 2. Is it a dedicated PG host?  How many hyper threads and memory do 
> you have?
Yes dedicated PG host, 56 hyper threads and 380Go of memory.
> 3. Does PGBouncer run on another host or on the same host as PG?

I have a primary / stanby configuration using repmgr for replication.

PGbouncer is running on both of them.


@Tom, thanks i will have a look at this parameter.


"One thing that you might not have noticed is that "jit" defaults to on 
as of v12. Turning it off would prevent this specific crash case. (The 
fact that it's a crash comes from llvm's crummy error handling :-() You 
might still have OOM problems, but with luck they'd not take down the 
whole database."

Regards.