From: Tom Lane <tgl@sss.pgh.pa.us>
To: kjonca@fastmail.com
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Random crashes - segmentation fault
Date: Wed, 13 Nov 2019 10:07:03 -0500
Message-ID: <6161.1573657623@sss.pgh.pa.us> (raw)
In-Reply-To: <87tv77digm.fsf@alfa.kjonca>
References: <871rucdwkt.fsf@alfa.kjonca>
<20191113125832.GZ1549@paquier.xyz>
<87tv77digm.fsf@alfa.kjonca>
kjonca@fastmail.com (Kamil =?iso-8859-2?Q?Jo=F1ca?=) writes:
> Michael Paquier <michael@paquier.xyz> writes:
>> Could it be possible to see a backtrace of the crash? There is
> Erm. Only thing I can do is to configure for debug future crashes. Could you
> tell me what and how to configure to get backtrace?
There's some accumulated wisdom at
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
I'd suggest that before worrying about that, you should install 12.1
(official release is tomorrow) and see if the crashes go away. There's
not much info in this report, but it could match any of several
already-fixed bugs.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, kjonca@fastmail.com, michael@paquier.xyz
Subject: Re: Random crashes - segmentation fault
In-Reply-To: <6161.1573657623@sss.pgh.pa.us>
References: <871rucdwkt.fsf@alfa.kjonca> <20191113125832.GZ1549@paquier.xyz> <87tv77digm.fsf@alfa.kjonca> <6161.1573657623@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox