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 1os2j6-0000zf-FH for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 14:03:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1os2i7-00072q-66 for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 14:02:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1os2i6-00072a-Ra for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 14:02:46 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1os2hy-000599-Gc for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 14:02:44 +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 2A7E2QOm3192953; Mon, 7 Nov 2022 09:02:26 -0500 From: Tom Lane To: Stefan Froehlich cc: pgsql-general@lists.postgresql.org Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault In-reply-to: <20221107134710.GA7369@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> <20221107101716.GA20949@static.231.150.9.176.clients.your-server.de> <0fb331d6fa4743a89070e092c62020ffee3020a5.camel@cybertec.at> <54262965-310e-327b-d7be-ef3e6a0ed2eb@gmail.com> <20221107134710.GA7369@static.231.150.9.176.clients.your-server.de> Comments: In-reply-to Stefan Froehlich message dated "Mon, 07 Nov 2022 14:47:10 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3192951.1667829746.1@sss.pgh.pa.us> Date: Mon, 07 Nov 2022 09:02:26 -0500 Message-ID: <3192952.1667829746@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Stefan Froehlich writes: > On Mon, Nov 07, 2022 at 08:17:10AM -0500, Mladen Gogala wrote: >> On 11/7/22 06:19, Laurenz Albe wrote: >>> Don't continue to work with that cluster even if everything seems OK now. >>> "pg_dumpall" and restore to a new cluster on good hardware. >> Why would that be necessary if the original machine works well now? > I can understand the idea not to trust hardware anymore once a (not > clearly identified) problem occured. > In this case new hardware would - for reasons beyond the scope of > this list - not be any more or less trustworthy than the existing > one and thus (IMO) not make any difference. Whether you want to continue to trust the hardware or not is your call. It'd still be recommendable to pg_dumpall and restore into a freshly-initdb'd cluster, because otherwise you can't be real sure that you identified and cleared all the data corruption. regards, tom lane