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 1os4HX-0005Qt-H5 for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 15:43:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1os4HW-0006qO-Co for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 15:43:26 +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 1os4HW-0006qE-28 for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 15:43:26 +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 1os4HU-0005yX-4W for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 15:43:25 +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 2A7FhLAm3238318; Mon, 7 Nov 2022 10:43:21 -0500 From: Tom Lane To: Ron cc: pgsql-general@lists.postgresql.org Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault In-reply-to: <8ce71818-c3f3-84a1-8f66-e1ae9f6c0f79@gmail.com> 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> <3192952.1667829746@sss.pgh.pa.us> <8ce71818-c3f3-84a1-8f66-e1ae9f6c0f79@gmail.com> Comments: In-reply-to Ron message dated "Mon, 07 Nov 2022 08:40:21 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3238316.1667835801.1@sss.pgh.pa.us> Date: Mon, 07 Nov 2022 10:43:21 -0500 Message-ID: <3238317.1667835801@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ron writes: > On 11/7/22 08:02, Tom Lane wrote: >> 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. > Why *just* pg_dumpall instead of "pg_dumpall --globals-only" and parallel > (for speed) dumps of databases? [ shrug... ] Sure, if you like to make your life complicated. regards, tom lane