| From: | Murthy Nunna <mnunna(at)fnal(dot)gov> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Running rsync backups in pg15 |
| Date: | 2024-11-08 16:53:25 |
| Message-ID: | DM8PR09MB66779BE5DA062DFB7257BE96B85D2@DM8PR09MB6677.namprd09.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Yes, I know. Exclusive backups are removed.
From release notes of 15:
* Remove long-deprecated exclusive backup mode<https://www.postgresql.org/docs/15/continuous-archiving.html#BACKUP-BASE-BACKUP> (David Steele, Nathan Bossart)
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2024-11-09 04:54:54 | Re: Running rsync backups in pg15 |
| Previous Message | Scott Ribe | 2024-11-08 16:29:55 | Re: Running rsync backups in pg15 |