-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify that the Postgres version is 17 or newer on incremental backups #942
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Let's squash the commits (code and black reformat)
I do agree. Rebase, squash and merge @bleidens |
@bleidens I can see you force pushed a few minutes ago, likely to add some changes from |
@barthisrael Yes, I just finished resolving the conflicts with the previous merge, I will now take a look at the new conflicts in |
Performing an incremental backup using Postgres mode requires the Postgres server's version to be 17 or newer. This PR builds from the validation methods introduced by BAR-160 (`validate_backup_args` and `_validate_incremental_backup_configs`), adding a check for the Postgres server's version and issue an error if it's not compatible with incremental backups (<17). References: BAR-163 Signed-off-by: Barbara Leidens <barbara.leidens@enterprisedb.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after rebase and squash looks good to me
Performing an incremental backup using Postgres mode requires the Postgres server's version to be 17 or newer. This PR builds from the validation methods introduced by BAR-160 (
validate_backup_args
and_validate_incremental_backup_configs
), adding a check for the Postgres server's version and issue an error if it's not compatible with incremental backups (<17).References: BAR-163