While working on the new list-backup (BAR-207), a bug was spotted in the method is_full_and_eligible_for_incremental from the LocalBackupInfo class.
The method was using the volatile information backup_method of the server configuration. This would be harmful if the user creates backups with backup_method='postgres' and changes to 'rsync'. When using list-backup or show-backup commands, the user would get an error. To fix this, we just need to use the mode field from the backup.info object, which is what this commit is doing.
While working on the new list-backup (BAR-207), a bug was spotted in the method
is_full_and_eligible_for_incrementalfrom theLocalBackupInfoclass.The method was using the volatile information
backup_methodof the server configuration. This would be harmful if the user creates backups with backup_method='postgres' and changes to 'rsync'. When using list-backup or show-backup commands, the user would get an error. To fix this, we just need to use themodefield from thebackup.infoobject, which is what this commit is doing.References: BAR-228