From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_basebackup, manifests and backends older than ~12 |
Date: | 2020-04-11 00:41:18 |
Message-ID: | 20200411004118.zzodwbuidju6bxmh@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2020-04-10 16:32:08 -0400, David Steele wrote:
> On 4/10/20 4:09 AM, Michael Paquier wrote:
> >
> > I have noticed that attempting to use pg_basebackup from HEAD leads to
> > failures when using it with backend versions from 12 and older:
> > $ pg_basebackup -D hoge
> > pg_basebackup: error: backup manifests are not supported by server
> > version 12beta2
> > pg_basebackup: removing data directory "hoge"
> >
> > This is a bit backwards with what we did in the past to maintain
> > compatibility silently when possible, for example look at the handling
> > of temporary replication slots. Instead of an error when means to
> > force users to have to specify --no-manifest in this case, shouldn't
> > we silently disable the generation of the backup manifest? We know
> > that this option won't work on older server versions anyway.
>
> I'm a bit conflicted here. I see where you are coming from, but given that
> writing a manifest is now the default I'm not sure silently skipping it is
> ideal.
I think we at the very least should add a hint about how to perform a
backup without a manifest.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-04-11 00:49:05 | Re: Corruption during WAL replay |
Previous Message | Masahiko Sawada | 2020-04-11 00:30:30 | Re: SyncRepLock acquired exclusively in default configuration |