Re: pg_combinebackup fails on file named INCREMENTAL.*

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Subject: Re: pg_combinebackup fails on file named INCREMENTAL.*
Date: 2024-04-17 14:14:28
Message-ID: CA+TgmobKrqbAn_Fn4CVcwvQ5qyHanm1s2HHnMZeFppR9E4s_NQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 16, 2024 at 9:25 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Apr 15, 2024 at 10:12 PM David Steele <david(at)pgmasters(dot)net> wrote:
> > Anyway, I think it should be fixed or documented as a caveat since it
> > causes a hard failure on restore.
>
> Alright, I'll look into this.

Here's a patch.

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

Attachment Content-Type Size
v1-0001-Restrict-where-INCREMENTAL.-NAME-files-are-recogn.patch application/octet-stream 5.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2024-04-17 14:28:08 Re: Parallel CREATE INDEX for BRIN indexes
Previous Message Tom Lane 2024-04-17 14:00:23 Re: Speed up clean meson builds by ~25%