| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_basebackup, manifests and backends older than ~12 |
| Date: | 2020-04-11 23:08:17 |
| Message-ID: | 20200411230817.GA2250@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 10, 2020 at 04:44:34PM -0400, David Steele wrote:
> On 4/10/20 4:41 PM, Stephen Frost wrote:
>> It's only the default in v13.. Surely when we connect to a v12 or
>> earlier system we should just keep working and accept that we don't get
>> a manifest as part of that.
>
> Yeah, OK. It's certainly better than forcing the user to disable manifests,
> which might also disable them for v13 clusters.
Exactly. My point is exactly that. The current code would force
users maintaining scripts with pg_basebackup to use --no-manifest if
such a script runs with older versions of Postgres, but we should
encourage users not do to that because we want them to use manifests
with backend versions where they are supported.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-04-11 23:21:16 | Re: pg_validatebackup -> pg_verifybackup? |
| Previous Message | Tomas Vondra | 2020-04-11 22:44:45 | Re: sqlsmith crash incremental sort |