Page 1 of 1

comp going slow/compress not working

PostPosted: Thu Nov 06, 2008 3:09 am
by mishink7
My computer is going slow a bit when I turn on the PostgreSQL, and I think it may be due to all the hands I have, and that I havent compressed it or anything like that. I am using poker tracker omaha and whenever I try to compress the database I get an error looking like this.

An error has occurred. The error was:
7-SQLState = xx000
Error:could not read block 748 of relation 1663/16403/16443: Invalid Argument;
Error while executing the query.

Can anyone help me with this, and also is there other ways to make the database run more efficiently and make it faster?
Thanks.

Re: comp going slow/compress not working

PostPosted: Thu Nov 06, 2008 3:25 am
by mishink7
I searched the forums and I found a previous post that deals with this issue. It says to create a new database and backup the hand histories that I have, I am doing this now.

Re: comp going slow/compress not working

PostPosted: Thu Nov 06, 2008 4:03 am
by mishink7
I created a new database and the compress function now works and my computer is running a little faster, but it is still a little bit slow. Is there other ways to improve this?

Re: comp going slow/compress not working

PostPosted: Thu Nov 06, 2008 10:23 am
by kraada
Try following the steps in the Performance Tuning: PostgreSQL and Peformance Tuning: Hard Drives as that can generally improve performance.

What compress function are you talking about though? The Housekeeping will always take a while at this point and there isn't much (other than the above links give you) that can be done to improve performance.

Re: comp going slow/compress not working

PostPosted: Thu Nov 06, 2008 3:26 pm
by mishink7
oops, this is the pokertracker 3 forum. I am using PTO, that is why I have compress for vacuum/analyze and not housekeeping.

Is there some performance tuning for PTO?

Re: comp going slow/compress not working

PostPosted: Thu Nov 06, 2008 4:16 pm
by kraada
I'm not aware of any but feel free to ask in the PTO forum as mike is much more knowledgeable about PTO than I.

highfalutin