Re: BUG #5130: Failed to run initdb:1 - Mailing list pgsql-bugs

From flamin dragon
Subject Re: BUG #5130: Failed to run initdb:1
Date
Msg-id 5b6d05b80910230521iba07936vd8e785cb40488176@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5130: Failed to run initdb:1  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-bugs
2009/10/23 Craig Ringer <craig@postnewspapers.com.au>

> Robert Haas wrote:
>
> > Well, I'm sort of hoping one of the Windows folks will chime in
> > here...  but I would start by checking that PostgreSQL is in your path
> > exactly once and that the permissions are set right.
>
> It could also be a character coding issue or an issue caused by the
> localization of Windows paths.
>
> Robert: does your system actually have a directory called "C:\Program
> Files" ?
>
> If you open the Run dialog in the Start menu, paste in:
>
>  "C:\Program Files"
>
> including the quotes, and press enter, does any folder open? (Note that
> even if no "program files" folder is visible in C:\ in Windows Explorer
> it might still open; Windows virtualises some paths).
>
> --
> Craig Ringer
>
Yes it does have, and when I paste in Run dialog
 "C:\Program Files" it opens

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: BUG #5130: Failed to run initdb:1
Next
From: "Timothy Madden"
Date:
Subject: BUG #5136: Please drop the string literal syntax for CREATE FUNCTION ...