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..
In response to
pgsql-hackers by date
|Next:||From: ju219721||Date: 2008-09-19 08:29:40|
|Subject: Re: gsoc, oprrest function for text search take 2|
|Previous:||From: Simon Riggs||Date: 2008-09-19 08:25:43|
|Subject: Assert Levels|
pgsql-admin by date
|Next:||From: Tore Halset||Date: 2008-09-19 08:29:32|
|Subject: unable to restore 8.2.5|
|Previous:||From: Tom Lane||Date: 2008-09-18 23:03:11|
|Subject: Re: type unknown? |