DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=QoL1+7XTutLaprk74p1KAxws7xO31AEQ8dxgIV+H7yunXKQYf5x386O5/aoYezSWL/
	5EvT35qABPBXBOTH4FyjR+Q+NJWyZG2hT63iclAS/wcYZmjtPeAm+h7qeTywzqmWLYvn
	KaWrIUFiNaw0XQ3H9zefVbOdWetP4aEVJK2Sk=
Message-ID: <dcc563d10809190739w5c32a2e0j8ba07b59b8afbd87@mail.gmail.com>
Date: Fri, 19 Sep 2008 08:39:14 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Bernt Drange" <badrange@gmail.com>
Subject: Re: Regaining superuser access
Cc: pgsql-admin@postgresql.org
In-Reply-To: 
 <66fbdb9b-7a01-42c5-896c-0c5ffbe2f4fb@79g2000hsk.googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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>

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=F3:
>>
>> > 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=3Dxxx 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.