Re: Regaining superuser access

From: "Tim Bruce - Postgres" <postgres(at)tbruce(dot)com>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Regaining superuser access
Date: 2008-09-19 16:22:43
Message-ID: 38560.192.136.50.130.1221841363.squirrel@sm.tbruce.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Fri, September 19, 2008 07:39, Scott Marlowe wrote:
> On Fri, Sep 19, 2008 at 2:26 AM, Bernt Drange <badrange(at)gmail(dot)com> wrote:
>> On Sep 18, 7:03 pm, alvhe(dot)(dot)(dot)(at)commandprompt(dot)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(at)postgresql(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message kevin kempter 2008-09-19 21:51:07 Errors installing contrib
Previous Message Scott Marlowe 2008-09-19 14:39:14 Re: Regaining superuser access

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-09-19 16:43:53 Re: gsoc, oprrest function for text search take 2
Previous Message Tom Lane 2008-09-19 16:11:02 Re: [PATCHES] libpq events patch (with sgml docs)