Re: [BUGS] BUG #14683: *** glibc detected *** SELECT: double freeor corruption - Mailing list pgsql-bugs

From Ray Warren
Subject Re: [BUGS] BUG #14683: *** glibc detected *** SELECT: double freeor corruption
Date
Msg-id 4DD2043D33498E4B82FF57B256C47540D565F3@ex-04.aam.local
Whole thread Raw
In response to Re: [BUGS] BUG #14683: *** glibc detected *** SELECT: double free or corruption  (Michael Paquier <michael.paquier@gmail.com>)
List 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
thisresolved.
 

Thanks ... Ray


-----Original Message-----
From: Michael Paquier [mailto:michael.paquier@gmail.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.warren@artsalliancemedia.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

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Noah Misch
Date:
Subject: Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAMmessage.
Next
From: Ray Warren
Date:
Subject: Re: [BUGS] BUG #14683: *** glibc detected *** SELECT: double freeor corruption