On 29/04/15 09:12, Bruce Momjian wrote:
> On Fri, Feb 6, 2015 at 08:25:42AM -0500, Robert Haas wrote:
>> On Thu, Feb 5, 2015 at 10:21 PM, Ian Barwick wrote:
>>> I stumbled on what appears to be inconsistent handling of double slashes
>>> in tablespace paths when using pg_basebackup with the
>>
On Fri, Feb 6, 2015 at 08:25:42AM -0500, Robert Haas wrote:
> On Thu, Feb 5, 2015 at 10:21 PM, Ian Barwick wrote:
> > I stumbled on what appears to be inconsistent handling of double slashes
> > in tablespace paths when using pg_basebackup with the
> > -T/--tablespace-mapping
> > option:
> >
> >
On Thu, Feb 5, 2015 at 10:21 PM, Ian Barwick wrote:
> I stumbled on what appears to be inconsistent handling of double slashes
> in tablespace paths when using pg_basebackup with the -T/--tablespace-mapping
> option:
>
> ibarwick:postgresql (master)$ mkdir /tmp//foo-old
[...]
> The attached pa
Hi
I stumbled on what appears to be inconsistent handling of double slashes
in tablespace paths when using pg_basebackup with the -T/--tablespace-mapping
option:
ibarwick:postgresql (master)$ mkdir /tmp//foo-old
ibarwick:postgresql (master)$ $PG_HEAD/psql 'dbname=postgres port=9595'
p
