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 1orgP0-0004lZ-7M for pgsql-general@arkaria.postgresql.org; Sun, 06 Nov 2022 14:13:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1orgOy-0003hh-N9 for pgsql-general@arkaria.postgresql.org; Sun, 06 Nov 2022 14:13:32 +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 1orgOy-0003hY-A7 for pgsql-general@lists.postgresql.org; Sun, 06 Nov 2022 14:13:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1orgOr-0006jx-M0 for pgsql-general@postgresql.org; Sun, 06 Nov 2022 14:13:31 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2A6ED8ZH3007239; Sun, 6 Nov 2022 09:13:08 -0500 From: Tom Lane To: Stefan Froehlich cc: pgsql-general@postgresql.org Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault In-reply-to: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de> References: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de> Comments: In-reply-to Stefan Froehlich message dated "Sun, 06 Nov 2022 12:18:20 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3007237.1667743988.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 06 Nov 2022 09:13:08 -0500 Message-ID: <3007238.1667743988@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Stefan Froehlich writes: > I followed the suggestion to trace down the faulty record, found and > fixed it. Now I can access that record again, but if I try to dump > the table I get: > | 2022-11-06 11:52:36.367 CET [2098-35] LOG: server process (PID 296473= 8) was terminated by signal 11: Segmentation fault > Whatever was "done" does not prevent the problem from being > reproducible. I tried to track down this faulty record as well, but > binary proves difficult with 25*10^6 rows if the server crashes and > rebuilds after each try. > Is there any reasonable way to proceed from here? contrib/amcheck might help to identify the faulty data (at this point there's reason to fear multiple corruptions ...). If you're running v14 or v15 there's a frontend for that called pg_amcheck. regards, tom lane