#1
|
||||
|
||||
Poker Tracker - Who Converted to PostgreSQL?
My database hit it's maximum size tonight (I've been doing a lot of datamining lately). I did some research on the PT forums and see that my options are to:
1. Create a new database for future hands. If I do this, I believe I will NOT be able to view the combined stats from both databases, which is something I would want to do. 2. Convert my Access database to PostgreSQL, which has no maximum file size limit. Apparently, this porcess can take a while, so it's best to run it over night. I've been bouncing around the PT forum, reading the pors (many) and cons (none, really) of doing the conversion, so I think I'm going to just go ahead and do it. Before I do though - in hopes that someone who knows what I am talking about is still awake and online at this hour - has anyone done this yet? How did it go? Any recommendations? Detailed instructions are here, for those interested: |
#2
|
||||
|
||||
Standard.
When I was having "slow load" issues, I did some research on 2+2 and found out that this conversion is almost expected when you get to a certain level. You shouldn't have any problems. EDIT: I have not converted yet, but it's only a matter of time.
__________________
|
#3
|
||||
|
||||
Yeah, I came to the same conclusion. I found Mayhem on AIM, and he told me he converted too. He also gave me the great idea of keeping MY hands separately from my observed hands (in a second db). After I finish the conversion, I'll likely set that up. PAHud is able to combine the stats from multiple DBs, btw, so no need to clog up my db any more than it already is. "Whoops" on my past 5 days of observed hands.
Everything I read led me to believe this conversion would take forever and I wouldn't be able to do much on my computer while it was running, but so far anyway, mine is running quite smoothly and not affecting anything else. It's also going rather quickly too, so I expect it to be long done by the time I get up in the AM. |
#4
|
||||
|
||||
FYI - This went very smoothly for me. I followed the step by step instructions and had no problems at all. The actual conversion part took about 2.5 hours for me - not too bad.
Per Mayhem's suggestion, I'm going to make a new DB for dataming (Observed HHs) now. In fact, I think I may take it a step farther than that and make multiple new DBs for various limits that I'll be observing. |
#5
|
||||
|
||||
How many hands till you filled it up?
Also is it faster to refresh ?
__________________
I can only be Me, 'cause that is who I am! |
#6
|
||||
|
||||
What do you mean by "refresh" - I don't understand.
I had something like 1.2 million hands in my DB (on the summary page)... That's the TOTAL - you'd have to divide by 5+ to see how many unique hands. I'm not sure which number you mean. The version of PT I am running has a max db size of 1 GB. Newer ones apparently have a 2 GB max, but PostgreSQL has no max. BTW - I set up the new db for observed hands today. Including changing everything I needed to change in PT and PAHud, I'd say it took me 5 minutes. Well - not counting the actual CREATION of the new db (15 seconds, and then however long it took - I walked away). |
#7
|
||||
|
||||
Ring Game Statistics.
As you have it reading your hands while you are playing (set on a timer), it processes the new file and update the Ring game stats. Yeah I was wondering how many hands you had tracked in total. How many were you in (dealt cards).
__________________
I can only be Me, 'cause that is who I am! |
|
|