Re: BUG #15704: Possible causes for calling abort () system call during querying database.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: dr00487751(at)techmahindra(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15704: Possible causes for calling abort () system call during querying database.
Date: 2019-03-20 02:09:39
Message-ID: 20190320020939.GF3488@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 20, 2019 at 02:01:49PM +1300, Thomas Munro wrote:
> Just to rule something obvious out: did you make sure that libpq
> connections are never accessed by multiple threads at the same time?

More to the point: if you do that the memory handling of the internal
libpq structures gets heavily messed up, in ways similar to what your
report shows.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-03-20 08:15:14 Re: BUG #15703: Segfault in cancelled CALL-Statements
Previous Message Michael Paquier 2019-03-20 02:07:31 Re: BUG #15668: Server crash in transformPartitionRangeBounds