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 1orgkg-0005VO-8N for pgsql-general@arkaria.postgresql.org; Sun, 06 Nov 2022 14:35:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1orgke-0000ZO-Na for pgsql-general@arkaria.postgresql.org; Sun, 06 Nov 2022 14:35:56 +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 1orgke-0000XL-Bz for pgsql-general@lists.postgresql.org; Sun, 06 Nov 2022 14:35:56 +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 1orgkW-0006zW-Au for pgsql-general@postgresql.org; Sun, 06 Nov 2022 14:35:55 +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 2A6EZjck005455; Sun, 6 Nov 2022 15:35:45 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=froehlich.priv.at; s=hetzner1; t=1667745345; bh=BliQSOUgowsZs3GVMj0ygKH0fyP/o5q9/1/AKBpVeaQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kE765gIAx5HigiQ7/utA5TE/7z834jspN0CP8n6nmFR1vQdin6uF4blG9i5F/djf0 ZZLExLMxJjZTzt+1fXpOti8fs/7BPxv6WLR8C3NqfMH/BMG3+2FmZOloyK/xnk215h 7gjHD5BgW/p7gq45ffNWc9O4Za2/Pr9xkZg2aIG4= Received: (from sfroehli@localhost) by hetzner1.epaxios.com (8.14.4/8.14.4/Submit) id 2A6EZikG005454; Sun, 6 Nov 2022 15:35:44 +0100 Date: Sun, 6 Nov 2022 15:35:44 +0100 From: Stefan Froehlich To: Tom Lane Cc: pgsql-general@postgresql.org Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault Message-ID: <20221106143544.GA4940@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3007238.1667743988@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:13:08AM -0500, Tom Lane wrote: > > | 2022-11-06 11:52:36.367 CET [2098-35] LOG: server process (PID 2964738) was terminated by signal 11: Segmentation fault > 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. I am using v13, but well: | # 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 | This probably means the server terminated abnormally | before or while processing the request. | The connection to the server was lost. Attempting reset: Failed. This seems to be quite fucked up ("how" would be a good question, too, but for the moment priority is to work around the problem). If I have to delete 1k records in this table, I'll do and survive, but first I have to find out which ones. Bye, Stefan