1
I recently attempted to install PostgreSQL on a Windows XP SP3 machine using the EnterpriseDB installer. The installation was not successful, probably because I did not remember to turn off my antivirus (MS Security Essentials). So I ran the uninstaller that was installed by the installer, removed a leftover object in my user account, turned off the antivirus and reset a firewall exception for the port and the process, and re-downloaded and re-ran the installer.
After this I have not been able to start the server using any of the standard methods. A helpful person on the EnterpriseDB Installation forum looked over the installation log for my second installation attempt and said that the installer was running in “upgrade mode”, apparently because the installer found some trace of the previous installation not removed by the uninstaller. See posting, here, for his comments and the complete installation log: http://forums.enterprisedb.com/posts/list/3879.page
What is the likely cause of a failure to completely uninstall such as this one? How can I either: 1) assure that the next time I run the uninstaller it runs to completion, or 2) check whether it has removed everything and remove any leftovers manually?
I think to do the latter I would need a complete list of all the places that the installer touches.
I would be grateful for any help or suggestions that anyone could offer.
Sincerely, andrewH
Do you need something that EnterpriseDB is offering that's not available in the free PostgresSQL? – jdigital – 2014-02-15T06:03:24.170
@jdigital EnterpriseDB publish installers for regular PostgreSQL on Windows, too. They're currently the main distribution channel, since Command Prompt stopped releasing their MSIs. – Craig Ringer – 2014-02-15T06:34:19.820
@CraigRinger You can do a "copy-install" of PostgresSQL, so you don't need to run an installer. However, until you pointed this out, I didn't realize that the zip for that also comes from the folks at EnterpriseDB. It's marked as an option for advanced users. This might help work around an installer problem, at least if you're happy with a simple configuration. – jdigital – 2014-02-15T06:40:24.013
@jdigital Yeah, but it shouldn't really be necessary. It looks like the user has mangled their installation by hand-deleting chunks of it. – Craig Ringer – 2014-02-15T06:44:53.060
Which version did you try to install, exactly? – and31415 – 2014-02-15T17:42:05.800
@jdigital No, I am not trying to install the enterprise version. I am using the EnterpriseDB installer because that is the recommended installation method for Windows on the PostgreSQL site. I was attempting to install version 9.3 – andrewH – 2014-02-17T03:20:13.913