Re: fix tablespace handling in pg_combinebackup - Mailing list pgsql-hackers

From Robert Haas
Subject Re: fix tablespace handling in pg_combinebackup
Date
Msg-id CA+Tgmoaiw1MFGLTaPv1Z1NJPZjhuE5GR=VFF_E7hS=oxDj3-Lw@mail.gmail.com
Whole thread Raw
In response to Re: fix tablespace handling in pg_combinebackup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fix tablespace handling in pg_combinebackup
List pgsql-hackers
On Fri, Apr 19, 2024 at 3:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> That would be a reasonable answer if we deem the problem to be
> just "the buildfarm is unhappy".  What I'm wondering about is
> whether the feature will be useful to end users with this
> pathname length restriction.

Possibly you're getting a little too enthusiastic about these revert
requests, because I'd say it's at least a decade too late to get rid
of pg_basebackup.

As discussed elsewhere, I do rather hope that pg_combinebackup will
eventually know how to operate on tar files as well, but right now it
doesn't.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Colin Caine
Date:
Subject: Re: Okay to remove mention of mystery @ and ~ operators?
Next
From: Tom Lane
Date:
Subject: Re: postgres_fdw fails because GMT != UTC