I recently had to do a system restore, after which neither PokerTracker nor Windows seemed able to recognize my postgres database (though it was still on the hard drive). I deleted and reinstalled the database, and set the new one as PokerTracker's active db.

At this point, PT is able to import hands and run the HUD with the proper stats, and the "Player Statistics" report under the "General" tab works fine, but the "Player Summary" report directly above it won't function. Instead of stats, I get the following:

Unable to execute query: SELECT (holdem_table_session_summary.id_limit), as "id_limit", (sum(holdem_table_session_summary.cnt_hands)) as "cnt_hands", (sum(holdem_table_session_summary.cnt_hands_won))

I get similar (though much longer) messages under the Hands, Sessions, Positions, and Winnings tabs, as well as in the "Player Summary" report under the Summary tab (but not in the "Site Summary" report).


So, what's wrong and how do I fix it? Thanks.

From the Database / Postgres FAQ, which may be relevant to your situation:

There are two main reasons for this kind of error. The first is a result of data corruption from a computer crash that requires reindexing your database. You can reindex your database from the PostgreSQL command prompt. Click Start --> Programs --> PostgreSQL --> Command prompt. At the prompt that appears, type “reindexdb -a” and hit enter. Be aware that if you have large databases this may take a while, so be patient and wait for it to finish.
(If the re-index doesn't work because you are not logged in as user 'postgres' enter: "reindexdb -U postgres -a").

The second reason for this error is a result of faulty hardware. You can set PostgreSQL to ignore these errors 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.

Reindexing fixed the problem. Thank you.