Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1orzC6-00087b-PB for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 10:17:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1orzC3-0004Xd-1J for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 10:17:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1orzC2-0004XU-9D for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 10:17:26 +0000 Received: from mail.epaxios.com ([5.9.99.247]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1orzBx-0008Ko-5g for pgsql-general@postgresql.org; Mon, 07 Nov 2022 10:17:25 +0000 Received: from hetzner1.epaxios.com (localhost.localdomain [127.0.0.1]) by mail.epaxios.com (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 2A7AHHjJ024071 for ; Mon, 7 Nov 2022 11:17:17 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=froehlich.priv.at; s=hetzner1; t=1667816237; bh=5rAFvWCX+e9/d8+6oJenvJrzB9BAy7se6uwtRc87Jp0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=d/qv3RRp53Pb5gHIVPzlOgr4r12FWYOEgZyMQ6U+gFcaX/6yr9nAKDlWsKByInupf cWm0wuYur/Ay0JPFqnYat+JLtR3YvMuJMd0EaMLUqrKQToGdDvn2Z3fdjyqhXr+hXD 2SvPjs+cp7RRHNuQhvUlKsR7z95dGVMLsTIii7MA= Received: (from sfroehli@localhost) by hetzner1.epaxios.com (8.14.4/8.14.4/Submit) id 2A7AHGNo024067 for pgsql-general@postgresql.org; Mon, 7 Nov 2022 11:17:16 +0100 Date: Mon, 7 Nov 2022 11:17:16 +0100 From: Stefan Froehlich To: pgsql-general@postgresql.org Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault Message-ID: <20221107101716.GA20949@static.231.150.9.176.clients.your-server.de> References: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de> <3007238.1667743988@sss.pgh.pa.us> <20221106143544.GA4940@static.231.150.9.176.clients.your-server.de> <3010779.1667746112@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3010779.1667746112@sss.pgh.pa.us> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Nov 06, 2022 at 09:48:32AM -0500, Tom Lane wrote: > Stefan Froehlich writes: > > | # create extension amcheck; > > | # select oid, relname from pg_class where relname ='faultytablename_pkey'; > > | [returns oid 537203] > > | # select bt_index_check(537203, true); > > | server closed the connection unexpectedly > Another idea is to try using contrib/pageinspect to examine each > page of the table. Its output is just gobbledegook to most > people, but there's a good chance it'd fail visibly on the > corrupted page(s). Fortunately I was able to identify a window of 100 records (out of 25 mio.) containing all the errors. After deleting and re-inserting those records everything seems to be ok (at least, pg_dump and "reindex database" work without errors). I suspect a bad RAM module to be the root of the problems. We'll see. Side question: If it is possible to simply delete and create such records is it necessary that the server *core* *dumps*? There could be a switch adding additional safety (at the cost of performance) which would make troubleshooting not only much faster but non-invasive for the other databases on the same server as well. Bye, Stefan