TRIAL VERSION - Unable to execute query

[WhiteRider]

Please try this: viewtopic.php?f=16&t=7893#p37362

[pokerpro]

Fantastic, WR.

Problem solved!

Should I continue to leave the
"zero_damaged_pages = on"
command in that text file?

[WhiteRider]

In that post it says "After the error has been resolved, it is highly recommend that you go back into your PostgreSQL config file and remove the line we just added."

[pokerpro]

Although it was resolved and working perfectly yesteday, the problem has re-emerged today.

I applied the same solution but this time, I am left with the error message and PT3 is basically non-functional.

I am very concerned that I may need to revert back to PT2 if PT3 non-functionality persists.

Please advise.

[pokerpro]

I have never had these problems with PT2 and its coming to the stage that I am very disappointed by PT3.

It was working fine under the trial, but a few days into the purchase it is totally non-functional.

I don't mind if I lose my hands, but I really do need to get PT3 working. I cannot afford to play without a read on opponents.

[pokerpro]

I shut the computer down, restarted and re-did the process yet again.

This time it is working (again).

I really don't know what is going on. PT3 switches from functionality to non-functionality in a random manner.

Please advise.

[WhiteRider]

There must be a problem in this database - you could create a new database and re-import into it.
(Have you manually entered any tournament summaries into this DB? Those aren't exported properly at the moment.)

If you still have the original HH files in the 'move processed files to' folder, manually import them; otherwise use the database management screen to Export your hands, then re-import them into a new database.

I'll try to get Derek/APerfect10 (who wrote the guide you've used) to have a look at this thread.

[APerfect10]

After setting zero_damaged_pages on, are you experiencing crashes or frequent lost connections to the database?

Best regards,

Derek

[pokerpro]

Hi Derek

It worked perfectly yesterday and also today so far!

The problem I was having was lost connections to the database, but its been stable for a couple of days (today and yesterday).

[fccman]

I had this same problem today using version 3 build 2 running vista home premium. I simply opened "services.msc" and restarted the postgre service and all was then fine after the service was restarted. Now the last tournament I played on full tilt when I got knocked out right on the bubble I immediately shut down the full tilt client much faster than normal possibly having something do with it I dunno but that was the sequence of actions. The postgre service was showing that it was running when I restarted it anyway.