New Release: 3.00 build 4

[kraada]

Mark,

There have been suggestions before to have tournament summaries not create players that don't already exist in the database. I'm not sure how soon that'd be coming, but it would certainly solve this for you if it were an option.

Joey,

That error means that your PostgreSQL database isn't running. Please check to make sure that your firewall isn't blocking PostgreSQL from starting (PostgreSQL needs access to port 5432), then restart PT3; PT3 will automatically start PostgreSQL unless it is blocked by an antivirus/firewall from starting.

[MysticJoey]

i turned my fw off and im still getting the same message, besides why would it suddenly block something when i didnt change anything just instaled new version of pt3 and it was doing smth with database at the start

[Thomas42]

We do plan on implementing Purge Players Without Hands for tournaments as well but it's a bit more complicated. If you're willing to do a little bit of work, though, someone did put together manual queries to clear out players from tournaments that have no hands in this thread.

I don't want to purge players without hands. Their finishing position, percentage of time they are in the money and so on is still very useful information to get an idea about what level they play on.

Of course, at the moment I can't easily get this information when playing. TourneyTime in PT2 had that info and it was very useful. When that and more details, that can be easily accessed from the HUD, is finally making its way into PT3 this information will once again be useful.

[kraada]

Joey,

I'm not exaclty sure why some firewalls/anti-viruses decide to block a program you want to run but it does seem to happen to others on occasion too. Have you tried rebooting your computer? Sometimes that clears things up for some people.

Thomas,

That's just one possible solution . . . I don't play a lot of tournaments, personally, but I can't imagine that I'd make any different action upon seeing that someone was 0/2 lifetime in big sunday tournaments. A player of literally any skill level can bust early from two tournaments.

And I doubt you're going to have regulars that you'd have 100+ results on that you'd never sat at a table with.

[Legalizeit2]

Legalizeit:

Please enable logging (Configure --> Options --> Logging Enabled and restart PT3) and bring that report up, then attach the C:\Program Files\PokerTracker 3\PokerTracker.log file to a support ticket and we'll look into what could be causing this for you. My initial guess would be a custom stat that is causing problems after it was cached or database corruption, but I couldn't be certain until I saw the complete error message.

Thanks for your support.
Kraada, my main problem is the extreamly slow import and housekeeping after the upgrade to build 4.
To my best recollection I have no customized stats.
I have 10 databases, checked 5 of them, the error message is from 1 database so far, but again, this is not my main concern, the "freezing" and extreamly slow import and housekeeping is, which occurs when running any of the 10 databases.

I just ordered a new disk controller card and a fast disk.
Will export/import everything, reinstall postgres and housekeep the lot, that will most probably solve the problem.

I could be wrong, but I think something happened between beta 23 and build 4 that caused this problem.

[kraada]

That should hopefully resolve the problem, yes.

You're the only person who seems to be having extreme slowness in these newer versions though, so if that doesn't resolve it for you, please follow up; I'd like to get this fixed for you.

[Legalizeit2]

That should hopefully resolve the problem, yes.

You're the only person who seems to be having extreme slowness in these newer versions though, so if that doesn't resolve it for you, please follow up; I'd like to get this fixed for you.

Thanks!
I tried exporting/importing some data into a new database and it worked fine, import numbers where normal and it didn't "freeze" my PC. Looks like my databases are corrupted for some reason (or at least half of them).
Since I'm going to install new disks I need to do export/import anyway, just need to figure out what RAID configuration I should choose (0 I guess).

Problem solved.

[kaisersoze]

It works fine for me.

I have 5 databases.

I up from beta23 (i housekeep all), then beta24 then build4.

[mteaney]

When I opened PT3 this evening I was advised that a new version was available but it gave me two choices of which to download: (1) New installations with PostgresSQL and (2) upgrading user without PostgresSQL. I take this to mean that I should download the version without Postgres SQL since I already have a version with PostgreSQL and I am uprgrading. Have I interpreted the instructions correctly?

[WhiteRider]

When I opened PT3 this evening I was advised that a new version was available but it gave me two choices of which to download: (1) New installations with PostgresSQL and (2) upgrading user without PostgresSQL. I take this to mean that I should download the version without Postgres SQL since I already have a version with PostgreSQL and I am uprgrading. Have I interpreted the instructions correctly?

Exactly right.