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 1r2ktH-000gdG-MW for pgsql-bugs@arkaria.postgresql.org; Tue, 14 Nov 2023 04:19:07 +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 1r2ktF-004wXB-8o for pgsql-bugs@arkaria.postgresql.org; Tue, 14 Nov 2023 04:19:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r2ktE-004wX3-Sj for pgsql-bugs@lists.postgresql.org; Tue, 14 Nov 2023 04:19:05 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r2ktC-006KV9-5U for pgsql-bugs@lists.postgresql.org; Tue, 14 Nov 2023 04:19:04 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-5431614d90eso7962513a12.1 for ; Mon, 13 Nov 2023 20:19:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1699935541; x=1700540341; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=qhgILFJ0gUmzJ5/bNZI5T5ViaUvbC0a1K3cdCXyZUb8=; b=MO8Do1r9Xkl5AbX230N1WA08+3htgS3+011DpxNLlb5c76kfUGye+K15swRCExscwJ bm/CG6d98JIdLzN9TtIqVPufvCrYoIrINWGu/bwtCkm/iUdoe+fYMlTySnGYvvBq8eYs 0a1HpDW+v95SCouZ1oHiukXmot/Iuj2NhxLhSJrls2AN13tsdo6C64eF8hfwXLoCfbbJ laQVkMYu4aetGDAes4gF1tQeazR7OL6A3i3GX/1b9nuj8EdjUvLK56tjAsawlUQ1Bni4 rS8DORjb1YRJdXegsJib6MdAxNIjcrq26z6Hd76bXuzIrEpwt6claI09Y2GlXwumYT5X xKyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699935541; x=1700540341; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=qhgILFJ0gUmzJ5/bNZI5T5ViaUvbC0a1K3cdCXyZUb8=; b=metb/OlsB1rZ/Fzieb252Ch7j7LEn1Y42tsDV0Hm/VIK68UvpTbnsedtsUDtxP0j9c sk13+zcIr0f3Bgqu3e48Fe9h9rjQb36VUW03etar33S8Wt/6xwtoEkuYY5Xp8W/+SLL+ W/FwN6LY/TYwXaVyd2XhETe7kIM27tH8587ks53NCORiiS2JyAvGgqezh+dBTejJu8OP 4C7LQHUkhOmVkrHlv0mMkKCsGEHzIR6iINE/6i/GN0p39E+0MQSk1VAMK0ID06r16ddW kNNm3awI2pIT0odoohwfYIFQSSE5vfEbaJ5Z/SAbRmrx4+/gtCujtzo9rtGNibGvrs5R LUVQ== X-Gm-Message-State: AOJu0YwUfAiiJPkkFI70JthOByT6ppBkzXA0DsIO3EthVEZur2MlHb26 B6h5leebtBcVNnwQU43aUZJWUQ== X-Google-Smtp-Source: AGHT+IHnUT+4Gk0kI9GEYhCGUYlLGfytizGRfSL8EyMR0ftpiTZ4rF8tiAwjir2kZLxsd3ttU5f54w== X-Received: by 2002:aa7:de18:0:b0:544:97d6:ba64 with SMTP id h24-20020aa7de18000000b0054497d6ba64mr6844698edv.0.1699935541002; Mon, 13 Nov 2023 20:19:01 -0800 (PST) Received: from localhost.localdomain (p50992f7c.dip0.t-ipconnect.de. [80.153.47.124]) by smtp.gmail.com with ESMTPSA id r26-20020aa7d15a000000b0053dfd3519f4sm4443850edo.22.2023.11.13.20.19.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Nov 2023 20:19:00 -0800 (PST) Message-ID: Subject: Re: BUG #18179: Cluster History Error From: Laurenz Albe To: Abdullah Ergin Cc: Michael Paquier , pgsql-bugs@lists.postgresql.org Date: Tue, 14 Nov 2023 05:18:59 +0100 In-Reply-To: References: <18179-c25cb10fdc41bbf5@postgresql.org> <6df759efadaf406cf72ee4440204b25aa4ca407f.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2023-11-14 at 00:04 +0300, Abdullah Ergin wrote: > Laurenz Albe , 13 Kas 2023 Pzt, 23:13 tarihinde= =C5=9Funu yazd=C4=B1: > > On Mon, 2023-11-13 at 22:42 +0300, Abdullah Ergin wrote: > > > I'm relatively new to database expertise, are you referring to the ab= solute path as follows: > > >=20 > > > postgresql.auto.conf; > > > #Recovery settings generated by pgBackRest restore on 2021-09-29 01:0= 4:40 > > > restore_command =3D '/usr/bin/pgbackrest --stanza=3Dmydb_stanza archi= ve-get %f "%p"' > >=20 > > Yes, precisely.=C2=A0 But if te executable is in /usr/bin, it should be= found > > anyway... Is there really a /usr/bin/pgbackrest on the standby server? > > pgBackRest is only installed on my master and backup servers. The directo= ry where > it is installed is '/usr/bin/pgbackrest.' > > However, pgBackRest is not installed on my replica server. Then you shouldn't use it in your "restore_command". Best comment that out= . This is no PostgreSQL bug. Yours, Laurenz Albe