Re: 3867653, EMM1 cluster issue on 23rd May--core generated --design feedback - Mailing list pgsql-general

From Simon Riggs
Subject Re: 3867653, EMM1 cluster issue on 23rd May--core generated --design feedback
Date
Msg-id CANbhV-FCvd0OTyyoDQ03BFkD97t2nu9qnjYojKQtrno-f5-nGQ@mail.gmail.com
Whole thread Raw
In response to RE: 3867653, EMM1 cluster issue on 23rd May--core generated --design feedback  (M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>)
List pgsql-general
On Mon, 12 Jul 2021 at 16:07, M Tarkeshwar Rao
<m.tarkeshwar.rao@ericsson.com> wrote:
>
> Hi All,
>
> We are getting following core with following use case:
>
> Case: We made max_connections as 15 and 10 different processes opening 15 connections with server. It is running
fine.But after few hours it giving following
 
>           core. When we increase the max_connections then core come again but it take more hours to come.
>
> Program terminated with signal 11, Segmentation fault.

Sounds like a memory leak. In libpq programs this is often caused by
forgetting to run PQclear().

-- 
Simon Riggs                http://www.EnterpriseDB.com/



pgsql-general by date:

Previous
From: Simon Riggs
Date:
Subject: Re: ERROR: invalid memory alloc request size when committing transaction
Next
From: Magnus Hagander
Date:
Subject: Re: Getting pg_stat_database data takes significant time