Re: Fix initdb for path with whitespace and at char - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Fix initdb for path with whitespace and at char
Date
Msg-id CAA4eK1Kdp=F7o_JZYa8y6a2uGPS51FdPaxExFHutqdT+fbdo6g@mail.gmail.com
Whole thread Raw
In response to Re: Fix initdb for path with whitespace and at char  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fix initdb for path with whitespace and at char
Re: Fix initdb for path with whitespace and at char
List pgsql-hackers
On Wed, Apr 30, 2014 at 3:57 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Heikki Linnakangas <hlinnakangas@vmware.com> writes:
>> This looks correct to me. popen() requires SYSTEMQUOTEs on Windows, like
>> system() does.

It seems right now  SYSTEMQUOTE is used before popen both for
Windows and non-Windows, ex. adjust_data_dir() in pg_ctl.c

> We might forget to use the wrapper function too, if it has a nonstandard
> name, no?  A better idea would be to redefine popen() and system() on
> Windows.  It looks like we're already using a #define to redefine popen().

Won't defining variant of popen just for Windows to add SYSTEMQUOTE
effect such (where currently it is used for both win and non-winows)
usage?  Also, I think we might want to remove use of SYSTEMQUOTE
before popen calls where ever it is currently used to avoid usage of the
same two times.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_get_viewdefs() indentation considered harmful
Next
From: Tom Lane
Date:
Subject: Re: Fix initdb for path with whitespace and at char