Question on caching

[Kn1ve]

I just recently imported a bevy of custom statistics, and caching time is currently running at over 24 hours. Having read through every thread I could find on the subject, it seems that this is "normal" enough, and I've verified that the postgre process is still using CPU and the C:\Program Files\PostgreSQL\8.3\data\base\ directory continues to increase in size.

My question is whether or not I can interrupt the caching process without losing all the progress made thus far, or if it needs to run to conclusion uninterrupted. I saw in another forum post that clustering can be interrupted & resumed at a later time without losing progress, and I'm hopeful the same is true of caching.

Related question: I'm currently running PT3.0, but will be downloading the 3.2 beta as soon as it comes out (Rush poker FTW!). Will I need to re-cache when I install the beta version? If so, it would seem there's not really any point in continuing to cache for 3.0.

[tarix]

My question is whether or not I can interrupt the caching process without losing all the progress made thus far, or if it needs to run to conclusion uninterrupted. I saw in another forum post that clustering can be interrupted & resumed at a later time without losing progress, and I'm hopeful the same is true of caching.

At this point in time caching cannot be resumed.

Related question: I'm currently running PT3.0, but will be downloading the 3.2 beta as soon as it comes out (Rush poker FTW!). Will I need to re-cache when I install the beta version? If so, it would seem there's not really any point in continuing to cache for 3.0.

There might have been an update of the database structure. If you want to run a few SQL queries on your database we can sort out if you will have to recache or not?

[Kn1ve]

I'd be willing to give it a try, though I'm not SQL literate (i.e. you'd have to spell out what I'd need to do). My instinct though is that it wouldn't be worth the trouble, as I'm just going to let the cache run for another 24 hours or so, and I'm going to install beta3.2 regardless when it comes out. If it requires a re-cache, then so be it, although I'll likely put that off for a while since I'll be using it for RushPoker, and won't need to incorporate my past HH's.

Regardless, I'll put a final update to this post when it's done caching, just to let you know how long it ultimately took.

[tarix]

Beta 30.2 is available for download now.

(I'll be right back with the SQL query.)

[tarix]

1) Run pgAdmin (Start -> PostgreSQL 8.3 -> pgAdmin III)
2) Double click your Postgres server.
3) If it prompts you for a password the default is 'dbpass'
4) Open the Databases and select your database.
5) At the top click the "SQL Notepad button.
6) Paste this query and click the player button

Code: Select all

select * from settings where setting_name = 'dbversion';


7) If the dbversion is 300038 then you will not have to recache.