Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdrRw-004zIw-4r for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 12:16:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qdrRt-009t0q-BP for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 12:15:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdrRs-009t0X-Vk for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 12:15:56 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdrRo-0033V5-Pw for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 12:15:55 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 2026A2FAC4F7 for ; Wed, 6 Sep 2023 14:15:49 +0200 (CEST) Received: from s979.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 10CD92E28FB5; Wed, 6 Sep 2023 14:15:49 +0200 (CEST) Received: from s471.loopia.se (unknown [172.22.191.5]) by s979.loopia.se (Postfix) with ESMTP id 0D8ED10BC42A; Wed, 6 Sep 2023 14:15:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s934.loopia.se ([172.22.191.6]) by s471.loopia.se (s471.loopia.se [172.22.190.35]) (amavisd-new, port 10024) with UTF8LMTP id T0dIAGqWeu73; Wed, 6 Sep 2023 14:15:48 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id BD3F97CEA55; Wed, 6 Sep 2023 14:15:48 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Pgbackrest Restore Error - Segmentation fault (core dumped) From: Daniel Gustafsson In-Reply-To: Date: Wed, 6 Sep 2023 14:15:48 +0200 Cc: "pgsql-general@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <485D5DB0-F5FE-4197-94ED-627F162F80DF@yesql.se> References: To: pgdba pgdba X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 6 Sep 2023, at 13:08, pgdba pgdba = wrote: >=20 > Hello, when I restore with Pgbackrest, I get the following error, I = couldn't find a solution when I researched, can you support? You might be better off raising this question on the pgbackreset Github = repo as an issue, where more pgbackrest developers are likely to see it. Are you able to repeat the issue such that you can get a stack trace = from it? That will be helpful for anyone trying to find the issue. The postgres = wiki has some information on getting a stack trace from a postgres process, = and while not the same the process is similar enough that it might be = helpful reading. -- Daniel Gustafsson