From: Bruce Momjian <bruce@momjian.us>
To: Ian Lawrence Barwick <barwick@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: First draft of the PG 15 release notes
Date: Wed, 11 May 2022 22:46:27 -0400
Message-ID: <Ynx1AzF+YN4FOv6q@momjian.us> (raw)
In-Reply-To: <CAB8KJ=j9VhsFXuN+xv5qzxQV7gj-6TKqqwVLSgz5zU7F8nHCYw@mail.gmail.com>
References: <YnqIT8kpiO3m6SD7@momjian.us>
<CAB8KJ=jmLBMAmxjcew12-yntb7m3FH-8A2+Qb7+RybZp1w9GOg@mail.gmail.com>
<Ynxqf4PxtbP7UtLH@momjian.us>
<CAB8KJ=j9VhsFXuN+xv5qzxQV7gj-6TKqqwVLSgz5zU7F8nHCYw@mail.gmail.com>
On Thu, May 12, 2022 at 11:40:17AM +0900, Ian Lawrence Barwick wrote:
> Looking at the release notes from the point of view of someone who has maybe
> not been following the long-running debate on removing exclusive backups:
>
> "Important-sounding backup thing is suddenly gone! What was that
> again? Hmm, can't
> find anything in the now-current Pg 15 docs [*], do I need to worry
> about this!?"
>
> [*] the backup section has removed all mention of the word "exclusive"
> https://www.postgresql.org/docs/devel/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
>
> versus:
>
> "Long-deprecated thing is finally gone, ah OK whatever".
>
> I am thinking back here to a point in my working life where the
> release notes were reviewed
> (by a team including non-Pg specialists) for potential issues when
> considering a major
> upgrade - from experience the more clarity with this kind of change
> the better so
> as not to unnecessarily raise alarm bells.
Ah, you are right. I thought I had "deprecated" in the text, but I now
see I did not, and we do have cases where we mention the deprecated
status in previous release notes, so the new text is:
Remove long-deprecated exclusive backup mode (David Steele, Nathan
Bossart)
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, barwick@gmail.com
Subject: Re: First draft of the PG 15 release notes
In-Reply-To: <Ynx1AzF+YN4FOv6q@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox