Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUqFU-0007eA-V7 for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 10:51:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iUqFT-00040S-NH for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 10:51:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUnlB-0005MS-RB for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 08:12:18 +0000 Received: from smtpo90.poczta.onet.pl ([213.180.149.143]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iUnl7-0005Od-Ds for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 08:12:16 +0000 Received: from alfa.kjonca (178235055163.warszawa.vectranet.pl [178.235.55.163]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: kjonca@poczta.onet.pl) by smtp.poczta.onet.pl (Onet) with ESMTPSA id 47Cclm2Kh5z1YVjFs for ; Wed, 13 Nov 2019 09:12:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=poczta.onet.pl; s=2011; t=1573632724; bh=ENxQPLA/9h7g4i//DK+AKpap137moCwL0DaEx+ea3Mc=; h=From:To:Subject:Date:From; b=LawQXk156ewylcEQd3cMGKQ8w3X6lVgHbThvdFhwosTJ76ZK01l7dnLrKyfSvBcsF wkfeAgOmYdCxhN8AJ/mmC9SA5wPFMZxILae2Zx13cze8mwmNsq8PGa5nbEkjIW9EHa Nf703gNTBXPCFWsht/257dkPmk7emBYUzOuaqGHo= Received: by alfa.kjonca (Postfix, from userid 1000) id 47Cclk3nWMzjYBZ; Wed, 13 Nov 2019 09:12:02 +0100 (CET) From: kjonca@poczta.onet.pl (Kamil =?iso-8859-2?Q?Jo=F1ca?=) 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> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable X-ONET_PL-MDA-SEGREGATION: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a copy of message sent to debian-user mailing list: select version(); version=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 ---------------------------------------------------------------------------= --------------------------------------- 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=F1ca) 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: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 2019-11-04 00:07:38 CET LOG: server process (PID 19244) was terminated b= y signal 11: Segmentation fault > 2019-11-04 00:07:38 CET DETAIL: Failed process was running: update queue= set priority =3D -3 ; > 2019-11-04 00:07:38 CET LOG: terminating any other active server process= es > [...] > 2019-11-04 00:07:39 CET LOG: all server processes terminated; reinitiali= zing > 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 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 2019-11-05 21:43:56 CET LOG: server process (PID 23233) was terminated b= y 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 process= es > [...] > 2019-11-05 21:43:57 CET LOG: all server processes terminated; reinitiali= zing > 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 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 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 --=20 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!