#1
|
|||
|
|||
PAhud Problem: Won\'t finish populating cache.
I just created a new postgresql database in pokertracker to try to speed up my system. So now I have 2 databases, both postgresql both open in pokertracker. I have both selected in PAhud as databases to be used. The problem now is that after I selected the new database in PAhud it started updating the database check, and it has been stuck doing it for many hours. Does this process just take a really long time or is there a problem I need to fix?
|
#2
|
|||
|
|||
Re: PAhud Problem: Won\'t finish populating cache.
How many hands are in the database?
|
#3
|
|||
|
|||
Re: PAhud Problem: Won\'t finish populating cache.
There were a lot in one of them and none in one of them, and the other is PLO and I have no idea about that one, but anyway it just took a really long time and is working fine now.
|
#4
|
|||
|
|||
Re: PAhud Problem: Won\'t finish populating cache.
I had exactly the same problem - I think its a corrupted database. I kind of worked round the problem by adding a new database and exporting the HHs from the previous corrupted DB to my hard drive and then imported them back to my new DB. Then I deleted the DB both in PT and C:, and it worked absolutely fine when I then tried to cache it.
|
#5
|
|||
|
|||
Re: PAhud Problem: Won\'t finish populating cache.
It could be a corrupt database, but if there are a lot of hands in the database, it is just going to take a long time to initially create the cache.
|
#6
|
|||
|
|||
Re: PAhud Problem: Won\'t finish populating cache.
Could you be more specific about 'long time'? I've run into the same problem...
|
#7
|
|||
|
|||
Re: PAhud Problem: Won\'t finish populating cache.
I've had reported times of over 12 hours before. It depends on a lot of factors: database size, vacuum frequency, harddrive fragmentation, memory available, etc.
|
|
|