From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: cleanup patches for incremental backup |
Date: | 2024-01-18 09:49:48 |
Message-ID: | CAEze2WjhdVCqEe_qqEok3NA6DwUdOGSBjAxzmYdAqiaaH1uRcg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 17 Jan 2024 at 21:10, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Wed, Jan 17, 2024 at 1:42 PM Matthias van de Meent
> <boekewurm+postgres(at)gmail(dot)com> wrote:
> > Sure, added in attached.
>
> I think this mostly looks good now but I just realized that I think
> this needs rephrasing:
>
> + To restore incremental backups the tool <xref
> linkend="app-pgcombinebackup"/>
> + is used, which combines incremental backups with a base backup and
> + <glossterm linkend="glossary-wal">WAL</glossterm> to restore a
> + <glossterm linkend="glossary-db-cluster">database cluster</glossterm> to
> + a consistent state.
>
> The way this is worded, at least to me, it makes it sound like
> pg_combinebackup is going to do the WAL recovery for you, which it
> isn't. Maybe:
>
> To restore incremental backups the tool <xref
> linkend="app-pgcombinebackup"/> is used, which combines incremental
> backups with a base backup. Afterwards, recovery can use <glossterm
> linkend="glossary-wal">WAL</glossterm> to bring the <glossterm
> linkend="glossary-db-cluster">database cluster</glossterm> to a
> consistent state.
Sure, that's fine with me.
Kind regards,
Matthias van de Meent
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2024-01-18 09:54:10 | Re: subscription disable_on_error not working after ALTER SUBSCRIPTION set bad conninfo |
Previous Message | Andrei Lepikhov | 2024-01-18 09:48:54 | Re: POC: GROUP BY optimization |