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 1qE9xR-00051s-SL for pgsql-admin@arkaria.postgresql.org; Tue, 27 Jun 2023 14:46:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qE9xQ-00059M-O6 for pgsql-admin@arkaria.postgresql.org; Tue, 27 Jun 2023 14:46:16 +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 1qE9xQ-00059D-D2 for pgsql-admin@lists.postgresql.org; Tue, 27 Jun 2023 14:46:16 +0000 Received: from mail.thelabyrinth.net ([45.56.70.56]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qE9xN-000nT7-CJ for pgsql-admin@lists.postgresql.org; Tue, 27 Jun 2023 14:46:15 +0000 Received: from [10.5.0.2] (unknown [62.182.98.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dsteele) by mail.thelabyrinth.net (Postfix) with ESMTPSA id 41F065465C for ; Tue, 27 Jun 2023 14:46:10 +0000 (UTC) Message-ID: <634ceaf1-abb1-8bcc-f7a4-bb407f468a25@pgmasters.net> Date: Tue, 27 Jun 2023 16:46:08 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: Postgresql Database cant start after restore using pgBackRest Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <484cbe3c-eb15-5327-df72-3338c17c7855@pgmasters.net> <29c782b4-9ae3-364d-bca9-44f48c340aa3@gmail.com> <81a5d38d-db54-30ff-0b7c-054a950c5641@pgmasters.net> <56d23ec9-dc1f-e5a0-b2f9-59999abc5251@gmail.com> From: David Steele In-Reply-To: <56d23ec9-dc1f-e5a0-b2f9-59999abc5251@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/27/23 12:12, Ron wrote: > On 6/27/23 03:26, David Steele wrote: >> On 6/27/23 07:41, Deo Felix wrote: >>> In the postgresql.auto.conf i have this configs >>> restore_command = 'pgbackrest --pg1-path=/var/lib/postgres/main >>> --stanza=data archive-get %f "%p"' >>> recovery_target = 'immediate' >>> recovery_target_timeline = 'current' >>> >>> But still I the database cant start >> >> You will need to redo your pgbackrest restore with >> --target-timeline=current and then restart postgres to start recovery >> with the correct settings. > > Is this standard procedure for an "in place" --delta restore? No -- this is mitigation for the split-brain situation which was causing the OP's recovery error. Regards, -David