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 1sg29C-00ElMH-Hv for pgsql-general@arkaria.postgresql.org; Mon, 19 Aug 2024 13:10:10 +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 1sg29A-002wO6-Ew for pgsql-general@arkaria.postgresql.org; Mon, 19 Aug 2024 13:10:09 +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 1sg29A-002wNv-3b for pgsql-general@lists.postgresql.org; Mon, 19 Aug 2024 13:10:08 +0000 Received: from mail-yw1-x112c.google.com ([2607:f8b0:4864:20::112c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sg298-000PLW-Hx for pgsql-general@postgresql.org; Mon, 19 Aug 2024 13:10:07 +0000 Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-685cc5415e8so42340437b3.3 for ; Mon, 19 Aug 2024 06:10:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724073005; x=1724677805; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=H/XTCSXaCciI2B5TKyW/5eCj6pylRkeKFXb/P8RDP78=; b=gXpYUx8OyEGJpPk6X+hNMirCkD7EBaKq/W3kBcyqLn+E3yfJGCAdRKtDpKni7DT4C6 SVEmyqCTp0cr6l27MMaAiBmEmTP70zSmnUrLY0GOP+Et4itvw+TQlFX1DgIXjm+LAIzu szl3JWgWCE4eMnlWnekvPdtXFkdb/gG4qHln7nra9V1r5uiLclrk5Z5IK/2EWz/DiLoG LQWw4XEhbss6R19iDGifIXUYrEVhEj9BCeHuMo7zZdrrgFMe8o2rZZ9FfbPBTDptJtBV 6pVLvI8HkVT8ygPaeROGvr7+SCMhv9KTRRESahZNf/RJqZg7IZeRrNo9Mfn6uNH3ShQ2 KmHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724073005; x=1724677805; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=H/XTCSXaCciI2B5TKyW/5eCj6pylRkeKFXb/P8RDP78=; b=ClV3HllYacJt3Q0iZSP8NcUUxHBZu+Xbv8H7B6xvJlHMLx/ZU8/ojoMiHf+VrvyONJ gax4yzXPJs2JT9ZwVj0Vjd6v4CbRfd7rtgBN/zJcqeC6//M+53DmVpq0m+4a1sPVT600 bT+GFZUWAPuJJFjAfJXCl870cn52T9Cn/nGFjVOayd67Am+ymtpgXhXXiY8CwlJjdg0H fV1KQ0Y+SfipL6QwC8WGeNlIgQugooBXF5+sLd7xF0U6+yrazZcPiNiMhvLeOJlhxZvO LJAA/WFtbRyDxj9HGgl2ZUa5Pr5emv2qGqHETGRnQQqq3NxBaSZy4tQXV1ON6C77dEW7 Ttdw== X-Gm-Message-State: AOJu0Yy5g2LNDOh8XhV81vL9rq2xgZfs1fdFQW7c1juuN/P0Z6SNpEwe RhdOJE6mQZ0MFTzJNw8kIdWxeh/N/gajx750DshA7oL7g2FMUhhoruJf51MHvePRe6rEt6731oJ Q9sbiTdE3j3KB3oPIMh3EMGGmUEZ9Jifg X-Google-Smtp-Source: AGHT+IGsPyBTLKe+mx5C7eUhDqWoJbU+O3MwBmJdDwvLK5Bv6TfIUXCTHsy7aO1n3xAeVNY+hdJ3MAMbyck8YwKs4gQ= X-Received: by 2002:a05:690c:dc8:b0:6ad:75f6:679f with SMTP id 00721157ae682-6b1b72b1ac1mr141283157b3.6.1724073005561; Mon, 19 Aug 2024 06:10:05 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Mon, 19 Aug 2024 18:40:05 +0530 Message-ID: Subject: WAL replication and Archive command for pgbackrest on same server conf To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000010465a062009071c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000010465a062009071c Content-Type: text/plain; charset="UTF-8" Hi List , I am trying to configure the pgbackrest on a live server ( RHEL9, EPAS16 and Pgbacrest .2.52) which is having a working WAL archive configuration to a standby server in postgresql.conf as follows 1. archive_mod =on 2. archive_level=replica 3. archive_command = 'cp %p /data/archive/%f' To do the pgbackrest conf on the same archive_command directive (So both the existing WAL configuration as well as my new pgbackrest option both will work smoothly. how to add an entry in line 3 ?? archive_command = 'pgbackrest --stanza=Demo archive-push cp %p /data/archive/%f ' Please correct me If I am doing wrong in the above line.. Thank you, Krish --00000000000010465a062009071c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi List ,

I am trying to configure the = pgbackrest=C2=A0 on a live server ( RHEL9, EPAS16 and Pgbacrest .2.52)=C2= =A0 which is having a working=C2=A0 =C2=A0WAL archive configuration=C2=A0 t= o a standby server in postgresql.conf as follows

<= br>
1. archive_mod =3Don
2. archive_level=3Dreplica
3. arc= hive_command =3D 'cp %p /data/archive/%f'=C2=A0=C2=A0


To do the pgbackrest conf on the same= =C2=A0 =C2=A0archive_command=C2=A0 =C2=A0directive (So both the existing WA= L=C2=A0configuration as well as my new pgbackrest option both will work smo= othly.=C2=A0 =C2=A0how to add an entry=C2=A0 in line 3=C2=A0 ??
<= br>
archive_command =3D 'pgbackrest --stanza=3DDemo=C2=A0 arc= hive-push=C2=A0 cp %p /data/archive/%f '


<= /div>

Please correct me If I am doing wrong in the above= line..


Thank you,
Krish= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
--00000000000010465a062009071c--