Re: pg_basebackup fails with long tablespace paths

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Oskari Saarenmaa <os(at)ohmu(dot)fi>
Cc: 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-24 13:12:16
Message-ID: 549ABBB0.5040908@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2014-12-24 13:16:18 Re: Moving RestoreBlockImage from xlogreader.c to xlogutils.c
Previous Message Peter Eisentraut 2014-12-24 13:10:46 Re: pg_basebackup fails with long tablespace paths