rtgoad
09-13-2008, 08:07 PM
I know getting the database to start has been an issue with a few people. After spending about 10 hours messing with settings, uninstalling programs, removing firewalls and avg, I've found the solution. More than likely, if the only problem you are experiencing is starting the database, the issue lies in your ethernet card. I have a killer ethernet card, which is used to reduce latency for gaming that unbeknownst to me made it impossible to connect to postgre with my previous settings. I plugged my ethernet cord into the built-in motherboard port and the database started instantly. Following this I went to my killer card settings and noticed it was in application mode, which one would think would be the proper mode for running the database. I then changed it to gaming mode which didn't work, and then went back to application mode. After going back to application mode the database actually started without conflict.
Ultimately, if you have a special card try the one built into your motherboard, if that doesn't work mess with the different settings/modes on your alternate card. I didn't realize some modes on specialized cards have built-in firewalls which could possibly cause postgre to not start.
Hope this helps those of you that are having this problem. gl
Ultimately, if you have a special card try the one built into your motherboard, if that doesn't work mess with the different settings/modes on your alternate card. I didn't realize some modes on specialized cards have built-in firewalls which could possibly cause postgre to not start.
Hope this helps those of you that are having this problem. gl