PokerTracker

hi, Whether you can look at a log "PokerTracker.log" in ticket 97692,
in which during process Rebuild Cache have many errors
"[000000CC][PostgresPreparedStatement (Error)] Unable to execute prepared query: prepared_statement_1; Reason: Fatal Error ()" and
"2010/09/28 02:00:21.453: [000000CC][PostgresPreparedStatement (Error)] Unable to execute prepared query: prepared_statement_1; Reason: Fatal Error (ERROR: could not read block 182026 of relation 1663/16403/16537: Invalid argument )"

Rebuild Cache update is 100 percent complete, but Whether it will be bad for the further normal work of database ? (may be me have damage SSD disk)

me use postgres 8.3.11 and PT3 - 3.07.4beta

Your ticket is in our system and I'm sure you'll get a response within the next few hours.

this ticket me make for forum, (may be if want see full LOG only), may be kraada know answer?

Did you delete or otherwise remove any files from the PostgreSQL/8.3/data/base/ directory?

me format SSd disk, then instal PostgreSQL and use EnterpriseDB Tuning Wizard and then import and update FIRST database (There are suspicions that with a problem disk)

A damaged disk could certainly cause problems like that.

On what such errors can be displayed further? (Considering that Update Cache completed on 100% and in game all ok)

I'd need to see more of the log to figure out what happened - there was some prepared statement that was not run because PostgreSQL could not read a specific file. The files are automatically numbered by PostgreSQL and vary by system so without knowing what statement failed and what data is unavailable I cannot say what damage may have resulted or what may or may not be correct in your database.