Message-ID: <38560.192.136.50.130.1221841363.squirrel@sm.tbruce.com>
In-Reply-To: <dcc563d10809190739w5c32a2e0j8ba07b59b8afbd87@mail.gmail.com>
References: 
 <355ba921-203b-4380-bee4-67209316be62@x35g2000hsb.googlegroups.com>
	<497334.45125.qm@web25803.mail.ukl.yahoo.com>
	<aaad999b-500f-4c13-a738-0a35bd443b23@m73g2000hsh.googlegroups.com>
	<20080918170326.GH3868@alvh.no-ip.org>
	<66fbdb9b-7a01-42c5-896c-0c5ffbe2f4fb@79g2000hsk.googlegroups.com>
	<dcc563d10809190739w5c32a2e0j8ba07b59b8afbd87@mail.gmail.com>
Date: Fri, 19 Sep 2008 09:22:43 -0700 (PDT)
Subject: Re: Regaining superuser access
From: "Tim Bruce - Postgres" <postgres@tbruce.com>
To: "Scott Marlowe" <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Reply-To: postgres@tbruce.com
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

On Fri, September 19, 2008 07:39, Scott Marlowe wrote:
> On Fri, Sep 19, 2008 at 2:26 AM, Bernt Drange <badrange@gmail.com> wrote:
>> On Sep 18, 7:03 pm, alvhe...@commandprompt.com (Alvaro Herrera) wrote:
>>> Bernt Drange escribió:
>>>
>>> > After a lot of fiddling with being able to enter single user mode on
>>> a
>>> > windows machine (I had to figure out how to run the command line as
>>> > the correct user, then for some reason -D didn't work, but SET
>>> > PGDATA=xxx worked), I finally managed to fix my problem.
>>>
>>> Hmm, the -D thing not working should probably be studied -- perhaps
>>> we're missing escaping something somewhere.  Does the PGDATA path
>>> contain spaces or weird chars?
>>
>> From memory the path was something like: F:\Postgresql Database\data.
>> I quoted it with double quotes. Without -D postgres.exe complained
>> about not finding the data path, with it postgres.exe complained about
>> not finding the config file, stating that it looked in (from memory
>> vague) F:\Postgresql Database\data\postgres\somethingmore. Adding the
>> --config-file parameter didn't help.
>>
>> Is this enough information for you to start digging a bit more? If
>> not, I might find the exact messages, but I'm reluctant to do it on
>> this production database..
>
> I'm pretty sure the problem is with the space between Postgresql and
> Database.  Not sure if it's fixed in later releases or not.
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
Part of the problem may be the embedded space, as was already mentioned
(even though it shouldn't be an issue).

A good test would be to use the 8.3 directory naming convention which you
can get on Windows by using the "dir /x" command.  On my system,
"C:\Program Files\" is shortened to "C:\PROGRA~1\".  Obviously, you'd have
to look at every directory in the fully qualified filename to pull the 8.3
pathname.

And I'll go back to lurking and learning on the list.

Tim
KB0ODU

-- 
Timothy J. Bruce

visit my Website at: http://www.tbruce.com
Registered Linux User #325725