Re: pg_verifybackup: TAR format backup verification

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>
Cc: Sravan Kumar <sravanvcybage(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_verifybackup: TAR format backup verification
Date: 2024-09-27 12:03:44
Message-ID: CA+TgmoZBPKaonc=rE0d7YUm3fzeQTftP6o=8vqFDe1AY2nmbrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 27, 2024 at 2:07 AM Amul Sul <sulamul(at)gmail(dot)com> wrote:
> Thank you, Robert. The code changes look much better now.

Cool.

> A few minor comments:
>
> + each tablespace, named after the tablespace's OID. If the backup
> + is compressed, the relevant compression extension is added to the
> + end of each file name.
>
> I am a bit unsure about the last line, especially the use of the word
> "added." I feel like it's implying that we're adding something, which
> isn't true.

If you add .gz to the end of 16904.tar, you get 16904.tar.gz. This
seems like correct English to me.

> Typo: futher

OK, thanks.

> The addition of simple_ptr_list_destroy will be part of a separate
> commit, correct?

To me, it doesn't seem worth splitting that out into a separate commit.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-09-27 12:04:20 Re: On disable_cost
Previous Message Tomas Vondra 2024-09-27 12:00:17 Re: Extension security improvement: Add support for extensions with an owned schema