Thread: Problems with the Windows 8.4.1 upgrade from 8.3 on non-C drive

Hi,
We have tried this at least with Windows 2008 64-bit server and the problem
is very reproducible (multiple systems):

1. Install 8.3 on some non-C drive (say E:\)
2. Run the 8.4.1 installer to upgrade this install
> it appears that the 8.4.1 doesn't realize 8.3 is even installed

Result: Installation fails with a permission problem. It seems certain files
from 8.3 are not able to be deleted. When I manually try to delete them,
even with the Administrator user, it fails. I ultimately needed to take
ownership and then give Full Control before I was allowed to delete them.

There is no problem with this upgrade on the C:\ drive.

Thanks
--
View this message in context:
http://old.nabble.com/Problems-with-the-Windows-8.4.1-upgrade-from-8.3-on-non-C-drive-tp27714508p27714508.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

The one-click installers are designed in such a way that you can have different major versions of postgresql co-exist on the same machine. Thats the reason, the 8.4.1 installer doesn't realize that 8.3 is even installed.


On 2/26/10 12:56 AM, dtrobert wrote:

Hi, 
We have tried this at least with Windows 2008 64-bit server and the problem
is very reproducible (multiple systems): 

1. Install 8.3 on some non-C drive (say E:\) 
2. Run the 8.4.1 installer to upgrade this install  

it appears that the 8.4.1 doesn't realize 8.3 is even installed    

Result: Installation fails with a permission problem. It seems certain files
from 8.3 are not able to be deleted. When I manually try to delete them,
even with the Administrator user, it fails. I ultimately needed to take
ownership and then give Full Control before I was allowed to delete them. 

There is no problem with this upgrade on the C:\ drive. 

Thanks 

I realize that this is a feature and not a bug, but what I ran into confronting the same issue was the fact that the servers listen on different ports and when I uninstalled the older version, the newer version was listening on a non-standard port.  This caused some confusion for awhile.