[CF2016-9] Allow spaces in working path on tap-tests - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject [CF2016-9] Allow spaces in working path on tap-tests
Date
Msg-id 20160704.160213.111134711.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
Responses Re: [CF2016-9] Allow spaces in working path on tap-tests  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Hello, this is just an entry mail for the next CF.

The tap-test fails when the soruce directoy containing spaces. I
accidentially hit this by a Jenkins project with the name "test
project".

The function system_log() is safe for such parameters but
backup() uses it in wrong way. On the other hand,
enable_restoring() and enable_archiving() forgets to quote such a
path containing spaces as already done for Windows. I don't see
the similar problem in other places.

regards,
-- 
Kyotaro Horiguchi
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: An extra error for client disconnection on Windows
Next
From: Michael Paquier
Date:
Subject: Renaming more clearly SHA functions in pgcrypto/