Page 1 of 1

Postgres Problem

PostPosted: Sun Aug 31, 2008 6:01 pm
by DonkKing
Hello,

I posted this problem in the housekeeping thread first and got a link to the FAQ section which deals with the database/postgres issues. Unfortunately I couln't find "my" error message in that FAQ section. However, I tried to fix the problem by following the instructions for a "reindex" of the database. I followed the instructions "Click Start --> Programs --> PostgreSQL --> Command prompt. At the prompt that appears, type “reindexdb -a” and hit enter.
(If the re-index doesn't work because you are not logged in as user 'postgres' enter: "reindexdb -U postgres -a").

I was asked to enter my password but couldn't type in a single letter (for both command options)

Therefore I post my problem again in this thread:

When trying to import either cash game or tournament hands, I get the following error message (it’s not just Everest, it occurs at Full Tilt or Poker Stars as well)

“Everest: Unable to import hand (#3643312360). Reason: Unable to execute query: COPY tourney_holdem_hand_player_statistics FROM STDIN;; Reason: Fatal Error (ERROR: invalid page header in block 1555 of relation "tourney_holdem_hand_player_statistics" CONTEXT: COPY tourney_holdem_hand_player_statistics, line 1: "9478 19934 19934 154 10 137 2008/08/31 19:33:11 9 f f 0 f 1 f f f t f 0 f 1 t f f t f 0 f 1 t f f t ..." )”


Full Tilt: Unable to import hand (#7880180980). Reason: Unable to execute query: COPY holdem_hand_player_statistics FROM STDIN;; Reason: Fatal Error (ERROR: invalid page header in block 4731 of relation "holdem_hand_player_statistics" CONTEXT: COPY holdem_hand_player_statistics, line 1: "30744 19946 19946 0 7 3565 2008/08/31 21:34:31 2 t t 0 f 1 t f f t f 1 t 0 f f f t f 0 f 0 f f f f f..." )


Cheers

Re: Postgres Problem

PostPosted: Sun Aug 31, 2008 9:27 pm
by kid hustlr
Hi, I had the exact same problem.

Just remove the need for a password by following this thread:
viewtopic.php?f=45&t=4510

Then follow the instructions you have been following (only now u wont need a password) and everything should work!

Re: Postgres Problem

PostPosted: Mon Sep 01, 2008 5:04 pm
by DonkKing
cheers. but I still have the same problem - after reindexing the database, I still get the same error message in PT :(

Re: Postgres Problem

PostPosted: Mon Sep 01, 2008 5:24 pm
by DonkKing
do I have to delete the postgres database and re-install ???? :o

Re: Postgres Problem

PostPosted: Tue Sep 02, 2008 4:23 am
by WhiteRider
I wonder if this will fix it:
viewtopic.php?f=16&t=7893#p37362

..but the error you're getting isn't quite the same so let me see if I can get Derek to have a look first.

Re: Postgres Problem

PostPosted: Thu Sep 04, 2008 12:33 am
by APerfect10
Yes, I think the instructions in the link WhiteRider provided above should work.

Best regards,

Derek

Re: Postgres Problem

PostPosted: Thu Sep 04, 2008 4:07 pm
by DonkKing
I tried this option, however it didn't work.
After trying first the reindexing of the database and then the "zero_damaged_pages = on", I still get the same error message.
Full Tilt: Unable to import hand (#7934682577). Reason: Unable to execute query: COPY holdem_hand_player_statistics FROM STDIN;; Reason: Fatal Error (ERROR: invalid page header in block 4731 of relation "holdem_hand_player_statistics" CONTEXT: COPY holdem_hand_player_statistics, line 1: "30749 11 11 21 3 3591 2008/09/04 20:05:25 2 f t 0 f 0 f t f f f 0 f 0 f f f f f 0 f 0 f f f f f 0 f ..." )


Is there another way left than deleting my database and doing a re-installation?

Re: Postgres Problem

PostPosted: Thu Sep 04, 2008 11:22 pm
by APerfect10
And you restart PostgreSQL or reloaded the configuration after setting 'zero_damaged_pages = on'?

That should have resolved the issue. Essentially what has happened is that there is a damaged block in the database which could be caused by a power failure, bad memory, bad hard drive, etc. Turning zero_damaged_pages on and PostgreSQL should simply ignore the error although you are losing the data from this block.

If that does not work then I am unsure except to remove the database, create a new one and re-import. :(

I also highly recommend that you run your Windows chkdsk command to check your hard drive for errors. A faulty hard drive will almost ensure this will happen again in the future and that is probably a best case scenario...

Best regards,

Derek