Re: backup manifests - Mailing list pgsql-hackers

From Robert Haas
Subject Re: backup manifests
Date
Msg-id CA+TgmoYjOmnNbo1cEm4aA-zxWzuP7t=jSHL3JA+0JRhjc9vnTA@mail.gmail.com
Whole thread Raw
In response to Re: backup manifests  (tushar <tushar.ahuja@enterprisedb.com>)
Responses Re: backup manifests  (tushar <tushar.ahuja@enterprisedb.com>)
List pgsql-hackers
On Mon, Mar 9, 2020 at 12:22 PM tushar <tushar.ahuja@enterprisedb.com> wrote:
> On 3/5/20 10:25 PM, Robert Haas wrote:
> > Here's an updated patch set responding to many of the comments
> > received thus far.
> Thanks Robert. There is a scenario - if user provide port of v11 server
> at the time of  creating 'base backup'  against pg_basebackup(v13+ your
> patch applied)
> with option --manifest-checksums,will lead to  this  below error
>
> [centos@tushar-ldap-docker bin]$ ./pg_basebackup -R -p 9045
> --manifest-checksums=SHA224 -D dc1
> pg_basebackup: error: could not initiate base backup: ERROR: syntax error
> pg_basebackup: removing data directory "dc1"
> [centos@tushar-ldap-docker bin]$
>
> Steps to reproduce -
> PG v11 is running
> run pg_basebackup against that with option --manifest-checksums

Seems like expected behavior to me. We could consider providing a more
descriptive error message, but there's now way for it to work.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "Rémi Lapeyre"
Date:
Subject: [PATCH v2] Allow COPY "text" to output a header and add header matching mode to COPY FROM
Next
From: Robert Haas
Date:
Subject: Re: recovery_target_action=pause with confusing hint