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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: ray(dot)warren(at)artsalliancemedia(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 01:18:17
Message-ID: CAB7nPqTQsohd_27We1RHLtZ9maawOwYBz27iRAK2h_suAsuqxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message wangchuanting 2017-06-02 01:33:30 Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog
Previous Message Michael Paquier 2017-06-02 00:28:16 Re: BUG #14682: row level security not work with partitioned table