Re: BUG #14683: *** glibc detected *** SELECT: double free or corruption

From: Ray Warren <Ray(dot)Warren(at)artsalliancemedia(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14683: *** glibc detected *** SELECT: double free or corruption
Date: 2017-06-02 08:20:58
Message-ID: 4DD2043D33498E4B82FF57B256C47540D565F3@ex-04.aam.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Michael,

I can't create a self-contained test case. This seems to be a random crash. It is happening daily at different time of day. The SQL running at the time isn't the same.

Is this likely a bug in Postgres? Could we have something misconfigured? This is a production system so we need to get this resolved.

Thanks ... Ray

-----Original Message-----
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
Sent: 02 June 2017 02:18
To: Ray Warren
Cc: PostgreSQL mailing lists
Subject: Re: [BUGS] BUG #14683: *** glibc detected *** SELECT: double free or corruption

On Thu, Jun 1, 2017 at 1:11 AM, <ray(dot)warren(at)artsalliancemedia(dot)com> wrote:
> We are experiencing some performance issues and we had this error on Sunday.
> Not sure whether the 2 things are related or not as we have been
> making some changes to the application and load. However, I assume the
> double free or corruption error is a bug?

Could you come up with a self-contained test case? It will be difficult to dig into this issue otherwise.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ray Warren 2017-06-02 08:43:34 Re: BUG #14683: *** glibc detected *** SELECT: double free or corruption
Previous Message Noah Misch 2017-06-02 06:32:16 Re: [PATCH] Fixed malformed error message on malformed SCRAM message.