> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Lee,
> Patricia S.
> Sent: 23 September 2005 17:46
> To: pgsql-hackers@postgresql.org; psql-novice@postgresql.org
> Subject: [HACKERS] PgAdmin3 1.2.2 Install on Win32 Disrupts Pg Service
>
> System: Windows XP Pro SP2
> Running Postgres 8.0.3 for several months with the embedded PgAdmin3
> 1.2.1 on the same machine with no problems. Postgres is configured to
> start automatically as a service. I installed the PgAdmin3 1.2.2 which
> requested a Windows reboot. I rebooted without stopping Postgres and
> then couldn't restart the Postgres service. Manual restarts
> with pg_ctl
> and postmaster commands complained that the user must not have admin
> privilege. So, I changed the user's group to non-privileged status and
> uninstalled PgAdmin3 1.2.2. Now, the Postgres service starts and runs,
> PgAdmin3 1.2.1 works (and PgAdmin3 1.2.2 works remotely) but pg_ctl
> status claims there's no postmaster nor postgres running. What might
> have the installation of PgAdmin3 1.2.2 done to upset this
> installation?
Nothing that I can imagine. It shops with the same versions of the
shared DLLs as come with 8.0.3 anyway, and everything else installs in
it's own directory and really doesn't care what else is installed. Even
if pgAdmin 1.2.2 installed a corrupted dll for some odd reason,
uninstalling it again wouldn't have caused the old file to be restored,
so things would still be broken.
I suspect the pgAdmin installation is a red herring to a whole different
problem. You could try running the PostgreSQL 8.0.3 installer to repair
the installation, then upgrade the pgAdmin.exe file within the embedded
installation with the one from the 1.2.2 pgAdmin installer.
Regards, Dave.
