| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Piyush Anand <piyush(dot)anand(at)ericsson(dot)com>, Mohammad Rizwan Ahmad <mohammad(dot)rizwan(dot)ahmad(at)ericsson(dot)com> |
| Subject: | Re: 3867653, EMM1 cluster issue on 23rd May--core generated --design feedback |
| Date: | 2021-08-12 09:25:52 |
| Message-ID: | CANbhV-FCvd0OTyyoDQ03BFkD97t2nu9qnjYojKQtrno-f5-nGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 12 Jul 2021 at 16:07, M Tarkeshwar Rao
<m(dot)tarkeshwar(dot)rao(at)ericsson(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-08-12 09:32:15 | Re: Getting pg_stat_database data takes significant time |
| Previous Message | Simon Riggs | 2021-08-12 09:19:01 | Re: ERROR: invalid memory alloc request size when committing transaction |