Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1k66pG-0002Vr-4K
	for pgsql-admin@arkaria.postgresql.org; Thu, 13 Aug 2020 06:34:58 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1k66oi-000521-Fg
	for pgsql-admin@arkaria.postgresql.org; Thu, 13 Aug 2020 06:34:24 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <mjoigny@neteven.com>)
	id 1k66oi-0004ye-5H
	for pgsql-admin@lists.postgresql.org; Thu, 13 Aug 2020 06:34:24 +0000
Received: from mail4.neteven.com ([5.135.111.119])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <mjoigny@neteven.com>)
	id 1k66oe-00020A-Ke
	for pgsql-admin@postgresql.org; Thu, 13 Aug 2020 06:34:23 +0000
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail4.neteven.com (Postfix) with ESMTP id 24B9918E35;
	Thu, 13 Aug 2020 08:34:19 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail4.neteven.com 24B9918E35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=neteven.com; s=dkim;
	t=1597300459; bh=6/Y85Vxmsyx1aHgnVJMRdQ4KJEB7HOaPg7aS7AUucmw=;
	h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To:From;
	b=hZ9nNLJMpWQpi4HmQrm6otuOwS8g0fOaDMr+sIEslwYqoz7tqoToUf/C4XzeAHFRb
	 J1J5MLpJwRPbiQw0pdGDfSQtt7gHV0PqyxrHpittQWHThOPiNjiWPAGRQnYLk4Vh+K
	 KdcOjq0e+BaVjP0DOrQKd4B3uvl2Pa4nHCWzZpxE=
X-Virus-Scanned: Debian amavisd-new at mail4.neteven.com
Received: from mail4.neteven.com ([127.0.0.1])
	by localhost (mail4.neteven.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xODOliVeGMOC; Thu, 13 Aug 2020 08:34:19 +0200 (CEST)
Reply-To: mjoigny@neteven.com
Subject: Re: PG 11.8 > PG 12.3 : Unable to allocate section memory
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: tgl@sss.pgh.pa.us, pgsql-admin@postgresql.org
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>
From: "JOIGNY Michael @Neteven" <mjoigny@neteven.com>
Message-ID: <8cf2b7ce-80db-f762-0629-a1a945c15285@neteven.com>
Date: Thu, 13 Aug 2020 08:34:18 +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: <eedaeeef-5372-f414-ed80-2c0a95ff377a@sqlexec.com>
Content-Type: multipart/alternative;
 boundary="------------3AEDC576CD4076DA16D42CFE"
Content-Language: en-US
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

This is a multi-part message in MIME format.
--------------3AEDC576CD4076DA16D42CFE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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


--------------3AEDC576CD4076DA16D42CFE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="tw-ta-container hide-focus-ring tw-nfl"
      id="tw-target-text-container" tabindex="0"><span lang="en">Since
        the deactivation of the JIT param, no more error message. <br>
      </span></div>
    <div class="tw-ta-container hide-focus-ring tw-nfl" tabindex="0"><span
        lang="en"><br>
      </span></div>
    <div class="tw-ta-container hide-focus-ring tw-nfl" tabindex="0"><span
        lang="en">Thanks for your help. <br>
      </span></div>
    <div class="tw-ta-container hide-focus-ring tw-nfl" tabindex="0"><span
        lang="en"><br>
      </span></div>
    <div class="tw-ta-container hide-focus-ring tw-nfl" tabindex="0"><span
        lang="en">Have a good day.</span></div>
    <div class="tw-ta-container hide-focus-ring tw-nfl" tabindex="0"><span
        lang="en"><br>
      </span></div>
    <div class="moz-cite-prefix">Le 12/08/2020 à 17:56, MichaelDBA a
      écrit :<br>
    </div>
    <blockquote type="cite"
      cite="mid:eedaeeef-5372-f414-ed80-2c0a95ff377a@sqlexec.com">Just
      to see if work_mem is related to these memory problems,  please
      lower it from 96MB to 16MB and do a reload:
      <br>
      pg_ctl -D &lt;your pg data directory&gt; reload
      <br>
      <br>
      If you still see memory problems, the problem is elsewhere. 
      Please report back.  Thanks.
      <br>
      <br>
      Don't forget to reset it back to 96MB if it's not the cause of the
      problem.
      <br>
      <br>
      Regards,
      <br>
      Michael Vitale
      <br>
      <br>
      <br>
      JOIGNY Michael @Neteven wrote on 8/12/2020 10:54 AM:
      <br>
      <blockquote type="cite">Hi Michael, Tom,
        <br>
        <br>
        Thanks for your help.
        <br>
        <br>
        Le 12/08/2020 à 16:26, MichaelDBA a écrit :
        <br>
        <blockquote type="cite">Please specify some other stuff:
          <br>
          <br>
          1. PG onprem or cloud? If cloud, which one and what instance
          type.
          <br>
        </blockquote>
        Onprem
        <br>
        <blockquote type="cite">2. Is it a dedicated PG host?  How many
          hyper threads and memory do you have?
          <br>
        </blockquote>
        Yes dedicated PG host, 56 hyper threads and 380Go of memory.
        <br>
        <blockquote type="cite">3. Does PGBouncer run on another host or
          on the same host as PG?
          <br>
        </blockquote>
        <br>
        I have a primary / stanby configuration using repmgr for
        replication.
        <br>
        <br>
        PGbouncer is running on both of them.
        <br>
        <br>
        <br>
        @Tom, thanks i will have a look at this parameter.
        <br>
        <br>
        <br>
        "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."
        <br>
        <br>
        Regards.
        <br>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Cordialement.
--------------------

NETEVEN
Michael JOIGNY
Service Exploitation - Ingénieur Systèmes
190 Avenue Jean Jaures - 75019 Paris
<a class="moz-txt-link-abbreviated" href="mailto:mjoigny@neteven.com">mjoigny@neteven.com</a> / <a class="moz-txt-link-abbreviated" href="mailto:adminsys@neteven.com">adminsys@neteven.com</a>
<a class="moz-txt-link-abbreviated" href="http://www.neteven.com">www.neteven.com</a></pre>
  </body>
</html>

--------------3AEDC576CD4076DA16D42CFE--