|
Yes, I know. Exclusive backups are removed. From release notes of 15:
If the database server stops abruptly while in this mode, the server could fail to start. The non-exclusive backup mode is
considered superior for all purposes. Functions pg_start_backup()/pg_stop_backup() have
been renamed to pg_backup_start()/pg_backup_stop(),
and the functions pg_backup_start_time() and pg_is_in_backup() have
been removed. Sorry my question was not clear. As per above release notes -
If the database server stops abruptly while in this mode, the server could fail to start. However, I crash tested in pg14 (stopped abruptly during exclusive
backup) but the cluster still started fine. Pg14 renamed backup_label to backup_label.old and restarted the cluster successfully. Repeating my question: What problem, if any, is resolved by removing exclusive backups in pg15 and above? There must be certain conditions other than just abrupt server crash which prompted the removal of
exclusive backups. Just trying to find what it is. |
