Date: Tue, 5 Dec 2023 15:48:43 +0100
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: "xuzhao.zhao" <xuzhao.zhao@qunar.com>
Cc: hailong.li@qunar.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Is it possible to add support for PostgreSQL-15 and newer
 versions in omnipitr?
Message-ID: <ZW84SzJV2slhlNeZ@depesz.com>
Reply-To: depesz@depesz.com
References: <04c32c47-d952-4da2-b274-b5a5ace2f007@qunar.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <04c32c47-d952-4da2-b274-b5a5ace2f007@qunar.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZW84SzJV2slhlNeZ%40depesz.com>
Precedence: bulk

On Tue, Dec 05, 2023 at 01:10:18PM +0800, xuzhao.zhao wrote:
> Hi depesz,
> We currently use omnipitr-backup-slave to backup our database for PG14 and
> earlier versions. However, there have been changes to the backup process in
> PG15 that have rendered omnipitr-backup-slave unable to function.
> Changes are as follows:
> 
>  * Functions pg_start_backup()/pg_stop_backup() have been renamed to
>    pg_backup_start()/pg_backup_stop()
>  * Remove long-deprecated exclusive backup mode. The connection calling
>    pg_backup_start must be maintained until the end of the backup, or
>    the backup will be automatically aborted.
> 
> Is it possible for the omnipitr-backup-slave tool to execute
> pg_start_backup() and keep the session open until it can also execute
> pg_stop_backup() after the tarball is created?

Hi,
that would take some not-trivial changes, and the code isn't really
maintained. I don't think the company that I developed it for even
exists anymore.

These days I would recommend migrating to something different like
pgbackrest, for example.

Best regards,

depesz