You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
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?
The text was updated successfully, but these errors were encountered: