Re: fix tablespace handling in pg_combinebackup

From: Andres Freund <andres(at)anarazel(dot)de>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fix tablespace handling in pg_combinebackup
Date: 2024-04-22 21:23:52
Message-ID: 20240422212352.ol7w24pjtyjypjok@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2024-04-23 09:15:27 +1200, Thomas Munro wrote:
> I find myself wondering if symlinks should go on the list of "things
> we pretended Windows had out of convenience, that turned out to be
> more inconvenient than we expected, and we'd do better to tackle
> head-on with a more portable idea".

Yes, I think the symlink design was pretty clearly a mistake.

> Perhaps we could just use a tablespace map file instead to do our own path
> construction, or something like that. I suspect that would be one of those
> changes that is technically easy, but community-wise hard as it affects a
> load of backup tools and procedures...)

Yea. I wonder if we could do a somewhat transparent upgrade by creating a file
alongside each tablespace that contains the path or such.

Greetings,

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-04-22 21:29:54 Re: [Doc] Improvements to ddl.sgl Privileges Section and Glossary
Previous Message David G. Johnston 2024-04-22 21:20:03 Re: [Doc] Improve hostssl related descriptions and option presentation