Unfortunately that's beyond my own SQL knowledge and I'm not aware of a method to create a statistic for that.

Are you also downloading and importing GGPoker tournament summary files in addition to the GGPoker hand history files? These are required to detect as much tournament data as possible: GGPoker Configuration Guide If you are not downloading and importing tournament summary files then those will need ...

Folks all I've done is update the software when prompted and now I'm having all sorts of issues, including backups and lost hands etc. This message is displayed when opening the app. I am a paying customer, I expect this to be resolved asap or I will be cancelling my subscription and requesting a f...

Security software can sometimes cause strange issues so if that's all you've installed I'd recommend completely uninstalling Malwarebytes, restarting your computer with Windows Defender active instead and then trying a fresh install of PostgreSQL to see how that behaves.

So i stupidly updated pt4 today and it obviously crashed and i lost my db which was upsetting but life goes on. If PokerTracker 4 were to crash databases are not just lost. What exactly happened? What version of PokerTracker 4 did you update from? Did you install PokerTracker v4.18.2 and it was unr...

Try saving the backup file to the root of C:\ instead of the default location and if you have 'Processed Hands' enabled under 'Optional Files' turn that off as well. If that doesn't resolve the issue then please turn on 'Enable Logging' in PokerTracker 4 via 'Configure -> Options' and then restart P...

Querying the data of a player that the statistic is not written for will require the addition of a subquery (which is unable to use the database cache ) like this: cash_hand_player_statistics.id_hand in (SELECT chps.id_hand from cash_hand_player_statistics chps, player p, cash_limit cl where chps.id...

If you want to add or edit tags you can do that via the 'Configure -> Tags' menu option:

Guide: Customizing Tags

A technician will be following up with you via your support ticket.

Unfortunately I've not seen anything like this before. If a completely different PostgreSQL install hasn't changed this behaviour then something with your device is likely causing this issue. Have you done a full virus scan on your computer? If you open a Support Ticket and attach your 5 latest Post...