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 1uqxj8-00Fwqh-IR for pgsql-admin@arkaria.postgresql.org; Tue, 26 Aug 2025 17:45: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 1uqxj7-008Xq7-JS for pgsql-admin@arkaria.postgresql.org; Tue, 26 Aug 2025 17:44:58 +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 1uqxj7-008Xpz-5Y for pgsql-admin@lists.postgresql.org; Tue, 26 Aug 2025 17:44:57 +0000 Received: from mx.ssan.egs-seg.gc.ca ([205.193.229.132]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uqxj3-001sgJ-22 for pgsql-admin@postgresql.org; Tue, 26 Aug 2025 17:44:56 +0000 Received: from DC01ZWH0032.corp.nrc.gc.ca ([167.37.58.21]) by mx.ssan.egs-seg.gc.ca with ESMTP id 57QHiq7g032153-57QHiq7i032153 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=CAFAIL) for ; Tue, 26 Aug 2025 13:44:52 -0400 Received: from DC01ZWH0029.Corp.nrc.gc.ca (167.37.54.15) by DC01ZWH0032.corp.nrc.gc.ca (167.37.58.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.10; Tue, 26 Aug 2025 13:44:47 -0400 Received: from DC01ZWH0029.Corp.nrc.gc.ca (167.37.54.15) by DC01ZWH0029.Corp.nrc.gc.ca (167.37.54.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.10; Tue, 26 Aug 2025 13:44:52 -0400 Received: from DC01ZWH0029.Corp.nrc.gc.ca ([fe80::f81b:b838:eba2:82ef]) by DC01ZWH0029.Corp.nrc.gc.ca ([fe80::f81b:b838:eba2:82ef%7]) with mapi id 15.02.1748.010; Tue, 26 Aug 2025 13:44:52 -0400 From: "Ghiurea, Isabella" To: PGSQL ADMIN Subject: using pgbackrest in a PG streaming replication cfg with repmgr Thread-Topic: using pgbackrest in a PG streaming replication cfg with repmgr Thread-Index: AQHcFrEgBBH4zLjayUWWejgLw/tqlw== Date: Tue, 26 Aug 2025 17:44:51 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [167.37.48.8] Content-Type: multipart/alternative; boundary="_000_d0939d84fc0f494f8aade7d3d0915f29nrccnrcgcca_" MIME-Version: 1.0 X-FEAS-Client-IP: 167.37.58.21 X-FE-Last-Public-Client-IP: 167.37.58.21 X-FE-Policy-ID: 25:37:97:SYSTEM DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=nrc-cnrc.gc.ca; s=slms3; c=relaxed/relaxed; h=from:to:subject:date:message-id:content-type:mime-version; bh=V4TQjFUmKVrlVCNRbhZpG9NQcrFtRv8LW58rzo+WQjY=; b=IW09V06Jic4QgI7BzLkSIxqHhTAkJ4OxNdpW+TgZRTeCiRfwMnthH5YOZ/d5+x7Hep5NP+BcR7vO 9whJhYK+n9/HkUucnSN7VcBiUdtEekYTmhbH2YuaJnyViF2lPAcILznUshqk6p208M3HNrB2vvgq gcNg0PcGlgVWC9XD9byRkkzUIZEulfFfnEqBYaIH0m8sWI0c4Ez5/emtTJ3Ji/6DXVuN6kwQx08J L8ddvv6KYwW9mYowPIJIGYZfa3LKVkF486j9mJQXykwRdRWaqmHMUuIrPQUkSzV9NrddLKEFWfaT qq7eRauNvmkPFyME6XqjlHOgaCOybFkNA2MkzA== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_d0939d84fc0f494f8aade7d3d0915f29nrccnrcgcca_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi List, We have a requirement to start using pgbackrest for db backups on slave = PG hosts already configured in Streaming Replication . To avoid any issu= es with WAL files transfer and performance in existing PG streaming repli= cation configuration , we plan to run pgbackrest only at a slave host and o= nly full database backups ( no need for PITR/incremental when already have= synchronous replication) . My questions are : -How do I cfg pgbackrest to not archive/use WAL files without affecting th= e synchronous streaming replication? - Are any known issues with pgbackrest + repmgr when running : repmgr stan= dby switchover ?( to promote a new db master while slave is online ) or r= epmgr promote ? thank you !!! --_000_d0939d84fc0f494f8aade7d3d0915f29nrccnrcgcca_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi List, 

We  have a requirement to start using pgbackrest for  db backu= ps  on slave PG hosts already configured in Streaming Replication = ; .   To avoid any issues with WAL files  transfer and perfo= rmance in  existing PG streaming replication configuration , we plan to run pgbackrest only at a slave host and only full database backups ( no= need for PITR/incremental  when already have synchronous replication)= . My questions are :

-How do I cfg pgbackrest to not archive/use WAL files  without affe= cting the synchronous  streaming replication?

- Are any known issues with pgbackrest + repmgr  when running := repmgr standby switchover  ?( to promote a new  db master = while slave is online ) or repmgr promote ?

thank you !!!




--_000_d0939d84fc0f494f8aade7d3d0915f29nrccnrcgcca_--