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 1iUt31-0006B6-4H for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 13:51:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iUt2z-0005k4-Je for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 13:51:01 +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 1iUsWA-0007ng-Mn for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 13:17:07 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iUsW7-0007xr-VH for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 13:17:05 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2BA5A2214C; Wed, 13 Nov 2019 08:17:03 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 13 Nov 2019 08:17:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= from:to:cc:subject:references:date:in-reply-to:message-id :mime-version:content-type:content-transfer-encoding; s=fm1; bh= ZBK4oUbHxKIs9szZiVraK/LhD0LsOwqaQiMH4SkEm64=; b=J+XoNMJH9eDovWvP FZGdpNxViMxVs4kjtaxNCVb44TcPh/zb+l+5XevgImj/UUgHe9wNmdHErD3YMA71 TnSSg3zepANmj7EDg7V++hy1OHSvHhrper1DHAlDffVHXSD9HA2ngcVGKq+QAhPr 4Rfb0hVrQcXKLZvWx8krQTnBPFQc2hBJXmIzieIpS8QeDXP+qBJTk8n2infKkpyL ofnfmRac8ZdcjMuPW0hAralGFfVAwbMLZfvMNQsozFBpm+1y25nVwWmuV0yPuqah eQnjPSnhYX83IVY1H4mU6eVKDql1MOGGYOb66/o2CPlrc6egudRfavjllxknsrb9 lYnvOw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=ZBK4oUbHxKIs9szZiVraK/LhD0LsOwqaQiMH4SkEm 64=; b=iBOjKgISBXjpXngtzAtaCOCc6Rtojg0nLigGyJ1f4j1LUjPB0U/5r4M3y 5MfYrewiBi+QyuUShuTIGgywRAYH9QCLeO27ybmRmGh8N/07JzHLt4jtJgNBt59A SB/726Ct11boNauOumA8Ix/R5gTK2RJc7KyfDjZ+T16kLbO59SknXIULq51hVtwZ 4xe3sAOQHgvOn9BMKX+Sr1WvkxIfftvwEGC1dBykrg1WAww9YINwyv1L76H3vlLz Ou4TjE49ySv+XGhUYu5V2L9sMtjR+xqAwmB9+bI6xn8SKrc2eELOQlO+lW8cyMiM 8HllQbiMyCxTS+YssXeVB/nHwew6Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudefuddghedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlvdefmdenucfjughrpefhvffufhffjgfkfgggtgfgsehtqhdttddt rehsnecuhfhrohhmpehkjhhonhgtrgesfhgrshhtmhgrihhlrdgtohhmucdlmfgrmhhilh culfhokngtrgdmnecuffhomhgrihhnpehsthhophhsthhophhnohhprdhplhenucfkphep udejkedrvdefhedrheehrdduieefnecurfgrrhgrmhepmhgrihhlfhhrohhmpehkjhhonh gtrgesfhgrshhtmhgrihhlrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from alfa.kjonca (178235055163.warszawa.vectranet.pl [178.235.55.163]) by mail.messagingengine.com (Postfix) with ESMTPA id 8DF698005C; Wed, 13 Nov 2019 08:17:02 -0500 (EST) Received: from kjonca by alfa.kjonca with local (Exim 4.93-RC1) (envelope-from ) id 1iUsW1-0007Dx-SB; Wed, 13 Nov 2019 14:16:58 +0100 From: kjonca@fastmail.com (Kamil =?iso-8859-2?Q?Jo=F1ca?=) To: Michael Paquier Cc: pgsql-bugs@lists.postgresql.org Subject: Re: Random crashes - segmentation fault References: <871rucdwkt.fsf@alfa.kjonca> <20191113125832.GZ1549@paquier.xyz> Date: Wed, 13 Nov 2019 14:16:57 +0100 In-Reply-To: <20191113125832.GZ1549@paquier.xyz> (Michael Paquier's message of "Wed, 13 Nov 2019 21:58:32 +0900") Message-ID: <87tv77digm.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 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Michael Paquier writes: > On Wed, Nov 13, 2019 at 09:12:02AM +0100, Kamil Jo=F1ca 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 --=20 http://stopstopnop.pl/stop_stopnop.pl_o_nas.html If I have trouble installing Linux, something is wrong. Very wrong. -- Linus Torvalds