Message-ID: <be58813938787fe100373f0de82021760d61ce15.camel@cybertec.at>
Subject: Re: Running rsync backups in pg15
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Murthy Nunna <mnunna@fnal.gov>, "pgsql-admin@postgresql.org"
	 <pgsql-admin@postgresql.org>
Date: Fri, 08 Nov 2024 11:23:04 +0100
In-Reply-To: 
 <DM8PR09MB667714AB7E04AB70B4B5A7B1B85C2@DM8PR09MB6677.namprd09.prod.outlook.com>
References: 
	<DM8PR09MB667714AB7E04AB70B4B5A7B1B85C2@DM8PR09MB6677.namprd09.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/be58813938787fe100373f0de82021760d61ce15.camel%40cybertec.at>
Precedence: bulk

On Thu, 2024-11-07 at 16:35 +0000, Murthy Nunna wrote:
> In PG14 and earlier, there is no requirement to keep database connection =
while rsync
> is in progress. However, there is a change in PG15+ that requires rsync t=
o be while
> we have the same database session open that executes SELECT pg_backup_sta=
rt('label').
> This change requires a rewrite of existing scripts we have.
> =C2=A0
> It can be done, but it makes it ugly to check errors and so forth that oc=
cur in the rsync script.
> =C2=A0
> Anybody found an elegant way of doing this?

You could try
https://github.com/cybertec-postgresql/safe-backup

Yours,
Laurenz Albe