On Fri, Sep 19, 2008 at 2:26 AM, Bernt Drange <badrange@xxxxxxxxx> wrote: > On Sep 18, 7:03 pm, alvhe...@xxxxxxxxxxxxxxxxx (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.
