pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: JOIGNY Michael @Neteven <mjoigny@neteven.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-admin@postgresql.org
Subject: Re: PG 11.8 > PG 12.3 : Unable to allocate section memory
Date: Thu, 13 Aug 2020 08:34:18 +0200
Message-ID: <8cf2b7ce-80db-f762-0629-a1a945c15285@neteven.com> (raw)
In-Reply-To: <eedaeeef-5372-f414-ed80-2c0a95ff377a@sqlexec.com>
References: <64eae88b-8ac5-366c-b6a2-e7b59b3d191b@neteven.com>
	<544598c0-8d92-b66b-e015-4fc7e5735c35@sqlexec.com>
	<1d659a5c-9b10-c92a-c901-e61aa1a0bcdc@neteven.com>
	<eedaeeef-5372-f414-ed80-2c0a95ff377a@sqlexec.com>

Since the deactivation of the JIT param, no more error message.

Thanks for your help.

Have a good day.

Le 12/08/2020 à 17:56, MichaelDBA a écrit :
> Just to see if work_mem is related to these memory problems,  please 
> lower it from 96MB to 16MB and do a reload:
> pg_ctl -D <your pg data directory> reload
>
> If you still see memory problems, the problem is elsewhere. Please 
> report back.  Thanks.
>
> Don't forget to reset it back to 96MB if it's not the cause of the 
> problem.
>
> Regards,
> Michael Vitale
>
>
> JOIGNY Michael @Neteven wrote on 8/12/2020 10:54 AM:
>> 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.
>>
>
-- 
Cordialement.
--------------------

NETEVEN
Michael JOIGNY
Service Exploitation - Ingénieur Systèmes
190 Avenue Jean Jaures - 75019 Paris
mjoigny@neteven.com / adminsys@neteven.com
www.neteven.com

view thread (6+ messages)

Message-ID: <8cf2b7ce-80db-f762-0629-a1a945c15285@neteven.com>
Permalink:  ../8cf2b7ce-80db-f762-0629-a1a945c15285@neteven.com/
Also on:    postgresql.org/message-id/8cf2b7ce-80db-f762-0629-a1a945c15285@neteven.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: mjoigny@neteven.com, MichaelDBA@sqlexec.com, tgl@sss.pgh.pa.us
  Subject: Re: PG 11.8 > PG 12.3 : Unable to allocate section memory
  In-Reply-To: <8cf2b7ce-80db-f762-0629-a1a945c15285@neteven.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox