1/2 Never backup a database that may already be corrupted. (if you restore it--> you'll restore a corrupted database)
Instead, export the new hands (since the last backup)
Restore the OLD (non-corrupted) backup--> import the new hands.
3 If pgadminIII shows "not responding", just ignore it, the program should unfreeze when the task is finished. Can take hours.
If you eventually get an error, it's a sign of a corrupt database.
4. go to RVG Software/HoldemManager/Importing folder/Logs folder and you
can see which hands couldn't be imported and resulted in errors.
5. The 2 most common causes of this problem are: powering off your
computer or having your computer lose power while the database is doing
something; and an old drive with bad sectors on it.
Basically what happens is a small portion of a file gets slightly
corrupt and then when you reboot and windows goes into that checkdsk
procedure it finds the bad section and, thinking it is doing a good
thing, removes it. Postgres then loads the table and a portion of it is
gone so it doesn�t like that and blocks access to the entire table.
Normally when this happens it is on a completely useless file that
you�ll never even notice is now gone but quite often it will happen to
an index in the DB which can easily be rebuilt but in your case it
happened to one or more of the tables.
So, to protect against this
1 - Keep your hands histories in case you do need to reimport
2 - Use a power bar and avoid hard shutdowns (when you flick the power switch on the pc)
3 - If your drive is old consider replacing it with a new one. They are cheap and much faster now than even a few years ago.