PokerTracker

After updating PT3 there is a problem with my database and Its all messed up.. Not really sure where to start but I can't Even get onto PT3 right now. It wants me to create a new database or connect to my old one, which it can't find.. It won't let me make a new one and I'm not quite sure whats going on, but I'm going to post a couple screen shots and we can go from there. '

I have quite a large database with over 500k hands so I really hope it can be saved.. I managed to (somehow) get into PT3 right after the update and saw most or all of my hands were still there, a few might of been missing.. I have not been able to get back on thought and had no Idea how I managed to, I just kept clicking cancel and trying to get out and it opened.


Here's what pops up when I open PT3



And when I try to find my database (clicking browse database) One of these 2 things happens:




And If I try to create a new one:

Those errors indicate that your PostgreSQL database is currently not running. Did you update anti-virus software recently?

Click Start --> Control Panel --> Administrative Tools --> Event Viewer and look in the Application section for errors relating to PostgreSQL - if you see any, double click them to get the error text and paste the text here as that will help explain why the server is not starting.

kraada wrote:Those errors indicate that your PostgreSQL database is currently not running. Did you update anti-virus software recently?

Click Start --> Control Panel --> Administrative Tools --> Event Viewer and look in the Application section for errors relating to PostgreSQL - if you see any, double click them to get the error text and paste the text here as that will help explain why the server is not starting.

I might have upgraded but I only use AVG free on this system.

In the last 24 hours there were about 150 errors involing PostgreSQL, would this be what you need?


FATAL: could not reattach to shared memory (key=5432001, addr=01D20000): Invalid argument

This error can occur for a couple reasons. The first is faulty hardware, and you should try setting PostgreSQL to use zero damaged pages by clicking Start --> Programs --> PostgreSQL --> Configuration Files --> Edit postgresql.conf. In the configuration file that appears, go to the bottom of the file and add the text "zero_damaged_pages = on" on a new line and then save and close the file. Click Start --> Programs --> PostgreSQL --> Reload Configuration and PostgreSQL will ignore the damaged data. If you continue to have problems with that hard drive, you should consider replacing it.

The second reason for this error may be a problem with the PostgreSQL autovacuuming daemon. Click Start --> Programs --> PostgreSQL --> Configuration Files --> Edit postgresql.conf and find the line that says "#autovacuum = on" and change it to "autovacuum = off" and save the file. Stop and restart PostgreSQL by clicking Start --> Programs --> PostgreSQL --> Stop Service, followed by Start --> Programs --> PostgreSQL --> Start Service and PostgreSQL should now be running properly.

Have the same proplem after a rebuilt of my XP system.

Event viewer said to PostgreSQL: GMT FATAL: Could not creat lock file "postmaster.pid": Permission denied

So i have to reinstall PostgreSQL, or is there another way to fix this problem?

Reboot your computer and then do a search for the "postmaster.pid". If you find it, delete the file and then attempt to start PostgreSQL again.