| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dilip kumar <dilip(dot)kumar(at)huawei(dot)com> |
| Subject: | Re: pg_basebackup vs. Windows and tablespaces |
| Date: | 2014-11-14 20:51:37 |
| Message-ID: | 54666B59.207@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Shulgin | 2014-11-14 21:11:36 | Idle transaction cancel/timeout and SSL revisited |
| Previous Message | Alvaro Herrera | 2014-11-14 20:36:53 | Re: New storage parameter pages_per_range not mentioned in CREATE INDEX doc |