Re: Failed to run initdb - not resolved bug 5130

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: Tomas Studva <tstudva(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Failed to run initdb - not resolved bug 5130
Date: 2010-01-03 02:33:04
Message-ID: 4B4001E0.7010702@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

John R Pierce wrote:
> Tomas Studva wrote:
>> My case is WIN XP SP 2 and also when applied SP3. My system has only
>> one speciality as I know, that is I have windows installed on F
>> partition.
>> ....
>> I was installing on path F:\Program Files\PostgreSQL\8.4 and also
>> tried C:\Program Files\PostgreSQL\8.4, problem is probably not with
>> install path.
>
> try a path without a space in it. I put mine on D:\Postgresql_84\

That _really_ shouldn't make a difference - and if it does, it's a bug.

I've had no issues with spaces in paths here.

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ben Woosley 2010-01-04 03:48:59 BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints
Previous Message Tomas Studva 2010-01-02 23:28:37 Re: Failed to run initdb - not resolved bug 5130