Upgrading 8.0.2 to 8.0.3 on Windows XP

Hello Giovanni,

I had a similar problem. I think the windows installer tries to create
a new service which he can't, since there is already one with the same
name. I uninstalled Postgresql but told it to keep the data directory,
rebooted the machine (that's important since only then the old service
is removed) and installed the new version, using the old data directory.

However, I would still do a dump before :-)

Hope this helps, Frank

Giovanni M. wrote:

Hello,

Wondering if somebody can help me out with upgrading a PostgreSQL 8.0.2
installation on Windows XP SP2.

I can�t seem to upgrade to 8.0.3 on a Windows XP Machine. The machine
has a limited user account running the pgsql-8.0 service. The first
installation was performed succesfully with the win32 installer.
A subsequent upgrade using the upgrade.bat file from the postgresql8.0.3
win32 distribution hangs at the very end with the following isntallation
error: "Verify
that you have sufficient privileges to start system services"... I must
cancel the installation at this point and it automatically performs a
rollback.

I cant seem to figure out why this keeps happening. I�m doing the
upgrade from an administrator account with all privileges, the limited
user account which runs the pgsql service has log on as service rights...

Anybody know a solution to this, or do I simply need to dump my
database, uninstall 8.0.2, do a fresh install of 8.0.3 and reload my
database?

Thanks in advance,

gio

--
A World of KEIGI
http://keigi.blogspot.com

--

Frank Rittinger

TERRAPLAN Geographische Informationssysteme
Gewerbestr. 33
79227 Schallstadt
Germany

Tel.: 07664-505315
Fax.: 07664-505321

http://www.terraplan.com

Hello Giovanni,

I had a similar problem. I think the windows installer tries
to create a new service which he can't, since there is
already one with the same name. I uninstalled Postgresql but
told it to keep the data directory, rebooted the machine
(that's important since only then the old service is removed)
and installed the new version, using the old data directory.

I've seen this happen a couple of times before, but I have no idea why
it happens :-( This is the correct workaround, though. It should be safe
enough. And note thaty ou don't have to "tell it to keep the data
directory" - the installer will *never* wipe your data directory. What
you have to tell it is not to initialize a new database (though it will
refuse to do this if you specify a directory that already contains a
database, if you specify a different one it will happily configure your
server against that directory instead).

If you manually stop the service first (I'm thinking it's somewhere
around this that the problem actually happens, but I've been unable to
figure out exactly where), you should not need to reboot. But the
installer should tell you if you need it or not.

The hardest part about this, and why this is not the default method, is
that you need to dig out the documentation of what service account
password you used last time you installed it. The upgrade.bat method
re-uses the existing identiy by just replacing the files.

However, I would still do a dump before :-)

*Always* do a dump before upgrading. Any database, any platform ;-)

//Magnus

ok guys thanks for the help. I will follow this advice to upgrade my
existing installation, I have already dumped by database as i keep backups
of course, and Im sure I can figure it out. I was just hoping I didnt need
to do much manual work, alas.

gio

On 8/15/05, Magnus Hagander <mha@sollentuna.net> wrote:

Hello Giovanni,

I had a similar problem. I think the windows installer tries
to create a new service which he can't, since there is
already one with the same name. I uninstalled Postgresql but
told it to keep the data directory, rebooted the machine
(that's important since only then the old service is removed)
and installed the new version, using the old data directory.

I've seen this happen a couple of times before, but I have no idea why
it happens :-( This is the correct workaround, though. It should be safe
enough. And note thaty ou don't have to "tell it to keep the data
directory" - the installer will *never* wipe your data directory. What
you have to tell it is not to initialize a new database (though it will
refuse to do this if you specify a directory that already contains a
database, if you specify a different one it will happily configure your
server against that directory instead).

If you manually stop the service first (I'm thinking it's somewhere
around this that the problem actually happens, but I've been unable to
figure out exactly where), you should not need to reboot. But the
installer should tell you if you need it or not.

The hardest part about this, and why this is not the default method, is
that you need to dig out the documentation of what service account
password you used last time you installed it. The upgrade.bat method
re-uses the existing identiy by just replacing the files.

However, I would still do a dump before :-)

*Always* do a dump before upgrading. Any database, any platform ;-)

//Magnus

--
A World of KEIGI
http://keigi.blogspot.com

--
A World of KEIGI
http://keigi.blogspot.com