pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: kjonca@poczta.onet.pl
To: pgsql-bugs@lists.postgresql.org
Subject: Random crashes - segmentation fault
Date: Wed, 13 Nov 2019 09:12:02 +0100
Message-ID: <871rucdwkt.fsf@alfa.kjonca> (raw)

This is a copy of message sent to debian-user mailing list:


select version();
                                                     version                                                       
------------------------------------------------------------------------------------------------------------------
PostgreSQL 12.0 (Debian 12.0-1+b1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 9.2.1-8) 9.2.1 20190909, 64-bit


kjonca@poczta.onet.pl (Kamil Jońca) writes:

> It is home PC box with debian sid.
> Recently my postgres was upgraded from version 11 to 12.
> I migrate databases, and during last few days I have had 2 server
> crashes.
> Crashes were during different statements. And after crash these
> statements executed successfully.
> In log I have:
> ===============================================================
> 2019-11-04 00:07:38 CET LOG:  server process (PID 19244) was terminated by signal 11: Segmentation fault
> 2019-11-04 00:07:38 CET DETAIL:  Failed process was running: update queue set priority = -3 ;
> 2019-11-04 00:07:38 CET LOG:  terminating any other active server processes
> [...]
> 2019-11-04 00:07:39 CET LOG:  all server processes terminated; reinitializing
> 2019-11-04 00:07:39 CET DEBUG:  mmap(150994944) with MAP_HUGETLB failed, huge pages disabled: Cannot allocate memory
> 2019-11-04 00:07:39 CET LOG:  database system was interrupted; last known up at 2019-11-04 00:02:24 CET
> ===============================================================
> 2019-11-05 21:43:56 CET LOG:  server process (PID 23233) was terminated by signal 11: Segmentation fault
> 2019-11-05 21:43:56 CET DETAIL:  Failed process was running: SELECT po_nr FROM get_free_numbers(999);
> 2019-11-05 21:43:56 CET LOG:  terminating any other active server processes
> [...]
> 2019-11-05 21:43:57 CET LOG:  all server processes terminated; reinitializing
> 2019-11-05 21:43:57 CET DEBUG:  mmap(150994944) with MAP_HUGETLB failed, huge pages disabled: Cannot allocate memory
> 2019-11-05 21:43:58 CET LOG:  database system was interrupted; last known up at 2019-11-05 21:43:49 CET
> ===============================================================
>
> any hints?
>
> KJ


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.)

KJ
-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
1.79 x 10^12 furlongs per fortnight -- it's not just a good idea, it's
the law!





view thread (6+ messages)  latest in thread

Message-ID: <871rucdwkt.fsf@alfa.kjonca>
Permalink:  ../871rucdwkt.fsf@alfa.kjonca/
Also on:    postgresql.org/message-id/871rucdwkt.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@poczta.onet.pl
  Subject: Re: Random crashes - segmentation fault
  In-Reply-To: <871rucdwkt.fsf@alfa.kjonca>
  References: <871rucdwkt.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