Re: pg_basebackup fails with long tablespace paths - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_basebackup fails with long tablespace paths
Date
Msg-id CA+Tgmoa0L+bFdDg2+2kN8Z3OrZ_ZvpNmYA4w=TW2z6W8W73kxw@mail.gmail.com
Whole thread Raw
In response to Re: pg_basebackup fails with long tablespace paths  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_basebackup fails with long tablespace paths  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Wed, Dec 24, 2014 at 8:12 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 12/22/14 10:00 PM, Amit Kapila wrote:
>> There is already a patch [1] in this CF which will handle both cases, so
>> I am
>> not sure if it is very good idea to go with a new tar format to handle this
>> issue.
>
> I think it would still make sense to have proper symlinks in the
> basebackup if possible, for clarity.

I guess I would have assumed it would be more clear to omit the
symlinks if we're expecting the server to put them in.  Otherwise, the
server has to remove the existing symlinks and create new ones, which
introduces various possibilities for failure and confusion.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
Next
From: Robert Haas
Date:
Subject: Re: Misaligned BufferDescriptors causing major performance problems on AMD