Re: Add notes to pg_combinebackup docs

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Martín Marqués <martin(dot)marques(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add notes to pg_combinebackup docs
Date: 2024-04-24 19:08:27
Message-ID: 8FDC557C-A58E-4F59-8BFE-153088BDB7C6@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 22 Apr 2024, at 20:52, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Apr 18, 2024 at 3:25 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>> On 18 Apr 2024, at 20:11, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-04-24 19:10:27 Re: New GUC autovacuum_max_threshold ?
Previous Message Robert Haas 2024-04-24 17:59:33 some additional (small) problems with pg_combinebackup and tablespaces