pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: kjonca@fastmail.com
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Random crashes - segmentation fault
Date: Wed, 13 Nov 2019 14:16:57 +0100
Message-ID: <87tv77digm.fsf@alfa.kjonca> (raw)
In-Reply-To: <20191113125832.GZ1549@paquier.xyz>
References: <871rucdwkt.fsf@alfa.kjonca>
	<20191113125832.GZ1549@paquier.xyz>

Michael Paquier <michael@paquier.xyz> writes:

> On Wed, Nov 13, 2019 at 09:12:02AM +0100, Kamil Jońca wrote:
>> Today (13.XI.2019 - KJ)  was another crash.
>> Another piece of a puzzle: There is (unlogged) table with 70M+
>> rows. After crash this table is empty (but table itself exists.)
>
> 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?
This is debian sid machine with postgres packaged by debian folks.
I guess I should enable core dumps. Anything else?

> nothing we can really do without any hint.  If you can send a
> self-contained test case which allows to reproduce the problem, that's
> even better.
I am afraid I cannot. These crasheas are rather rare and unpredictable.

> Please note that unlogged tables are reinitialized after
> a crash at the beginning of recovery.  That's their design.
I see. Thanks for explanation.

KJ


-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
If I have trouble installing Linux, something is wrong. Very wrong.
		-- Linus Torvalds





view thread (6+ messages)  latest in thread

Message-ID: <87tv77digm.fsf@alfa.kjonca>
Permalink:  ../87tv77digm.fsf@alfa.kjonca/
Also on:    postgresql.org/message-id/87tv77digm.fsf@alfa.kjonca

 · 

reply

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: kjonca@fastmail.com, michael@paquier.xyz
  Subject: Re: Random crashes - segmentation fault
  In-Reply-To: <87tv77digm.fsf@alfa.kjonca>
  References: <871rucdwkt.fsf@alfa.kjonca> <20191113125832.GZ1549@paquier.xyz> <87tv77digm.fsf@alfa.kjonca>

* 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