2022年5月11日(水) 0:44 Bruce Momjian <br...@momjian.us>: > > I have completed the first draft of the PG 15 release notes and you can > see the results here: > > https://momjian.us/pgsql_docs/release-15.html > > The feature count is similar to recent major releases: > > release-10 195 > release-11 185 > release-12 198 > release-13 183 > release-14 229 > --> release-15 186 > > I assume there will be major adjustments in the next few weeks based on > feedback.
Re this: >> Remove exclusive backup mode (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 requires a continuous database connection >> during the backup. It'd be useful to mention exclusive backup mode has been deprecated since 9.6, lest the impression arise that an important-sounding feature has been torn out suddenly. Also not sure why we need to mention that non-exclusive backup requires a continuous database connection, AFAIR that was also the case with exclusive backups. The patch also removed 4 and added 2 new functions, a change which anyone maintaining backup utilities would need to be aware of. Patch attached with suggested changes. Regards Ian Barwick -- EnterpriseDB: https://www.enterprisedb.com
diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml index 635941a908..997919bfb2 100644 --- a/doc/src/sgml/release-15.sgml +++ b/doc/src/sgml/release-15.sgml @@ -88,8 +88,17 @@ Remove exclusive backup mode (David Steele, Nathan Bossart) </para> <para> -If the database server stops abruptly while in this mode, the server could fail to start. The non-exclusive backup mode requires a continuous database connection during the backup. + Exclusive backup mode has been deprecated since PostgreSQL 9.6, when more flexible and reliable non-exclusive backups were introduced. </para> +<para> + Exclusive backup mode was limited to execution on a primary server and did not allow concurrent backups; moreover, in the event of a + database shutdown, in some circumstances manual intervention was required to enable the database to start up again. +</para> +<para> + As part of this change, the functions <function>pg_backup_start_time()</function> and <function>pg_is_in_backup()</function> were removed. + <function>pg_start_backup()</function> and <function>pg_stop_backup()</function> were renamed to <function>pg_backup_start()</function> and <function>pg_backup_stop()</function>. +</para> + </listitem> <!--
