Re: Add notes to pg_combinebackup docs - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Add notes to pg_combinebackup docs
Date
Msg-id 8FDC557C-A58E-4F59-8BFE-153088BDB7C6@yesql.se
Whole thread Raw
In response to Re: Add notes to pg_combinebackup docs  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Add notes to pg_combinebackup docs  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
> On 22 Apr 2024, at 20:52, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Thu, Apr 18, 2024 at 3:25 PM Daniel Gustafsson <daniel@yesql.se> wrote:
>>> On 18 Apr 2024, at 20:11, Robert Haas <robertmhaas@gmail.com> wrote:
>>> 2. As (1), but make check_control_files() emit a warning message when
>>> the problem case is detected.
>>
>> Being in the post-freeze part of the cycle, this seems like the best option.
>
> Here is a patch for that.

LGTM; only one small comment which you can ignore if you feel it's not worth
the extra words.

+    <literal>pg_combinebackup</literal> when the checksum status of the
+    cluster has been changed; see

I would have preferred that this sentence included the problematic period for
the change, perhaps "..has been changed after the initial backup." or ideally
something even better.  In other words, clarifying that if checksums were
enabled before any backups were taken this limitation is not in play.  It's not
critical as the link aptly documents this, it just seems like the sentence is
cut short.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: some additional (small) problems with pg_combinebackup and tablespaces
Next
From: Melanie Plageman
Date:
Subject: Re: New GUC autovacuum_max_threshold ?