Sorry Aleksander, but I can't really remember what I did. I had a
service running from a Cygwin install of Postgres, and I was messing
around with the command line for installing/uninstalling the service,
and had to reboot several times. I initially tried to change the path of
the sevice executable, and it was a big mess. This was the unzippable
version of Postgres from about a moth ago, so it is not really relevant
to this installer.
As an aside, Dave, can we get the \bin and \lib paths in the PATH
variable as part of the install? I am not sure if that will create a
mess if they are already there ...
Also, my PGDATA variable is still set at c:\postgres\data - but it does
not seem to have an effect on Postgres. I am going to try accessing
postgres with some python modules, and see what that does.
Cheers,
jp
En/na Aleksander Kmetec ha escrit:
>
> Johan Paul Glutting wrote:
>
>> When removing the service by hand using previous versions of
>> Postgres, the service was not removed from the Services panel until I
>> rebooted. This might be what is going on (WinXP here, though).
>
>
> Yes; rebooting seems to take care of it.
>
> Did you try reinstalling PG without rebooting?
> On my machine it fails - unless I specify a different service ID.
>
> It took me a couple of installs to figure out that just changing the
> sevice NAME doesn't work, in which case everything runs fine until
> right after cluster creation, when you get an error message saying
> that the service couldn't be installed, followed by rollback.
>
> The solution could be to try and detect any existing services with the
> same ID and refuse to go to the next step if one already exists.
>
> Regards,
> Aleksander
--
JP Glutting
Oficina de Qualitat Plaça Víctor Siurana, 1
Universitat de Lleida 25003 Lleida
-------------------------------------------------------
Tel: 973 703 103 Fax: 973 702 036