Re: is the base backup protocol used by out-of-core tools?
Bernd Helmle <mailings@oopsware.de>
From: Bernd Helmle <mailings@oopsware.de>
To: Robert Haas <robertmhaas@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers
<pgsql-hackers@lists.postgresql.org>, Etsuro Fujita
<etsuro.fujita@gmail.com>
Date: 2022-02-09T13:50:58Z
Lists: pgsql-hackers
Am Mittwoch, dem 09.02.2022 um 08:01 -0500 schrieb Robert Haas: > On Wed, Feb 9, 2022 at 3:14 AM Kyotaro Horiguchi > <horikyota.ntt@gmail.com> wrote: > > Thanks for pining. AFAICS, as you see, pg_rman doesn't talk > > basebackup protocol (nor even pg_basebackup command) as it supports > > inremental backup. So there's no issue about the removal of old > > syntax on our side. > > Cool. Since the verdict here seems pretty unanimous and we've heard > from a good number of backup tool authors, I'll give this another day > or so and then commit, unless objections emerge before then. > A while ago i worked on a tool which talks the streaming protocol directly. In the past there were already additions to the protocol (like MANIFEST), so to support those optional features and multiple major versions you already have to abstract the code to deal with that. Having said that, i don't have any objections either to remove the old protocol support. Thanks Bernd
Commits
-
Remove server support for the previous base backup protocol.
- 0d4513b61386 15.0 landed
-
Remove server support for old BASE_BACKUP command syntax.
- 9cd28c2e5f11 15.0 landed
-
Modify pg_basebackup to use a new COPY subprotocol for base backups.
- cc333f32336f 15.0 cited
-
Flexible options for BASE_BACKUP.
- 0ba281cb4bf9 15.0 cited