Re: pg_basebackup fails with long tablespace paths

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Oskari Saarenmaa <os(at)ohmu(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup fails with long tablespace paths
Date: 2014-12-28 01:02:52
Message-ID: CA+Tgmoa0L+bFdDg2+2kN8Z3OrZ_ZvpNmYA4w=TW2z6W8W73kxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 24, 2014 at 8:12 AM, Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-12-28 01:05:42 Re: Misaligned BufferDescriptors causing major performance problems on AMD
Previous Message Tom Lane 2014-12-28 00:55:05 Re: Better way of dealing with pgstat wait timeout during buildfarm runs?