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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: 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 01:01:49
Message-ID: CA+hUKGLLa6Piev1g25mGF83Q3YMf0qWMyK_tDsZc13ppuv9pqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 20, 2019 at 1:19 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> #18 0x00007fddcbba8908 in Thread::thread_router (objRun=0xf05960) at
> Thread.cpp:133

Just to rule something obvious out: did you make sure that libpq
connections are never accessed by multiple threads at the same time?

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-03-20 02:07:31 Re: BUG #15668: Server crash in transformPartitionRangeBounds
Previous Message Tom Lane 2019-03-19 21:30:30 Re: BUG #15705: psql autocompletion is not always correct with latest libedit