| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Dilip kumar <dilip(dot)kumar(at)huawei(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup vs. Windows and tablespaces |
| Date: | 2015-05-12 13:07:28 |
| Message-ID: | 5551FB10.1040505@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/12/2015 08:35 AM, Andrew Dunstan wrote:
>
> Yes, sorry, I had a moment of brain fade yesterday. However, I think
> we're a bit under-documented on the pg_basebackup page, regarding both
> tar mode and tablespace_map (which isn't even mentioned).
>
> And there is this which I noticed this morning: the
> --tablespace-mapping feature of pg_basebackup seems to be quite broken
> in --format=tar mode - it simply has no effect AFAICT. I assume it was
> broken before, but we should either fix it (possibly hard) or disallow
> the combination (which would be a pity).
>
> I'm going to go ahead and commit this in the state I have it now,
> because for the most part these are preexisting deficiencies.
>
>
One more thing: I think pg_basebackup will now not work in tar mode with
pre-9.5 servers, since it will be using an unrecognized option of the
BASE_BACKUP protocol command. If so that certainly needs to be
documented and release noted.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-05-12 13:10:07 | Re: RFC: Non-user-resettable SET SESSION AUTHORISATION |
| Previous Message | Robert Haas | 2015-05-12 13:00:14 | Re: Multi-xacts and our process problem |