| 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-13 00:56:02 |
| Message-ID: | 20200413005602.GB2169@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 12, 2020 at 08:08:17AM +0900, Michael Paquier wrote:
> 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.
Please note that I have added an open item for this thread, and
attached is a proposal of patch. While reading the code, I have
noticed that the minimum version handling is not consistent with the
other MINIMUM_VERSION_*, so I have added one for manifests.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| pgbasebackup-manifests-v1.patch | text/x-diff | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-04-13 01:18:28 | Re: where should I stick that backup? |
| Previous Message | Justin Pryzby | 2020-04-13 00:41:54 | Re: sqlsmith crash incremental sort |