Re: pg_basebackup vs. Windows and tablespaces - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_basebackup vs. Windows and tablespaces
Date
Msg-id 54666B59.207@gmx.net
Whole thread Raw
In response to Re: pg_basebackup vs. Windows and tablespaces  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_basebackup vs. Windows and tablespaces  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 11/13/14 4:33 PM, Peter Eisentraut wrote:
>> Is this still relevant after this commit?
>> > 
>> > commit fb05f3ce83d225dd0f39f8860ce04082753e9e98
>> > Author: Peter Eisentraut <peter_e@gmx.net>
>> > Date:   Sat Feb 22 13:38:06 2014 -0500
>> > 
>> >     pg_basebackup: Add support for relocating tablespaces
> I believe so.
> 
> The commit only applies to "plain" output.  Amit's complaint is that tar
> utilities on Windows don't unpack symlinks, so the "tar" format isn't
> useful on Windows when tablespaces are used.  So he wants the recovery
> mechanism to restore the symlinks.

Um, wouldn't accepting this patch break the above-mentioned
tablespace-relocation feature, because pg_basebackup wouldn't see any
more symlinks sent down?



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: New storage parameter pages_per_range not mentioned in CREATE INDEX doc
Next
From: Alex Shulgin
Date:
Subject: Idle transaction cancel/timeout and SSL revisited