From: | jseymour(at)LinxNet(dot)com (Jim Seymour) |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_ctl problem |
Date: | 2004-04-08 21:59:41 |
Message-ID: | 20040408215941.AD6714307@jimsun.LinxNet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alexander Cohen <alex(at)toomuchspace(dot)com> wrote:
>
[snip]
>
> so i tried passing this: ( added quotes to the problematic database
> path )
>
> ./pg_ctl start -w -D "/Volumes/GROUCH\ 2/Database3"
>
> and i still get the same error.
>
> Can i not pass a path with spaces in it?
Possibly with enough "escaping," you could do it. pg_ctl is itself a
shell script. So when it expands the argument to the -D switch, at
least one set of quotes will be lost. (Btw: The back-slash wasn't
really necessary.)
> How should i pass this command to the command line in order to get the
> server up and running?
You might be able to find some combination of escape sequences,
repeated escape sequences, etc., etc., to get it to work. But then, if
pg_ctl is subsequently changed to alter the way that argument is
processed: You're screwed.
I hate to answer a question with a question, but if ever there was a
case where doing so would appear legitimate, this, IMO, would have to
be it. So... Why in God's name are you trying to do this? Why not
just get rid of the space and save yourself the current, and possibly
future, grief?
--
Jim Seymour | Spammers sue anti-spammers:
jseymour(at)LinxNet(dot)com | http://www.LinxNet.com/misc/spam/slapp.php
http://jimsun.LinxNet.com | Please donate to the SpamCon Legal Fund:
| http://www.spamcon.org/legalfund/
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Seymour | 2004-04-08 22:31:32 | Re: Date Comparison Help |
Previous Message | Randall Skelton | 2004-04-08 20:41:38 | Re: extract epoch and index scanning |