Yes it does. I must have done it wrong the second time. Thanks again for all your hard work.

Do you just use the Postgre admin tool to run the queries, or is there something in PT I can't find...

How many times have I either been all in or against an all in player, and how many of those have I won?


select distinct sum(gp.won_hand) as num_hands_won, count(gp.*) as num_hands

from game g

inner join game_players gp
on gp.game_id = g.game_id

inner join prefs pr
on pr.pref_value = gp.player_id
and pr.pref_key = 'RP'

inner join game_players gp2
on gp2.game_id = g.game_id

inner join players p
on p.player_id = gp.player_id

inner join players p2
on p2.player_id = gp2.player_id

where p2.player_id != gp.player_id
and (gp.pre_flop_bet + gp.flop_bet + gp.turn_bet + gp.river_bet >= gp.chip_count
or gp2.pre_flop_bet + gp2.flop_bet + gp2.turn_bet + gp2.river_bet >= gp2.chip_count)
and gp2.went_to_showdown_n = 1
and gp.went_to_showdown_n = 1

Northview: The software developer in me cannot help but notice you have a "select distinct" there, 99% of the time the distinct keyword should be avoided, its slow, see article:

Often the results of a "select distinct" query can be replicated by adding a group by clause, without the performance hit.

Interesting - I'm a SQL Server developer, and there's no performance hit with SELECT DISTINCT over GROUP BY in that environment, as the Optimiser produces identical Execution Plans in both cases.

I guess PostGreSQL is a bit less forgiving in some respects.

I have NO idea how to use this... n00bster speaking, plz help

Only applies if you've converted your PT db to PostGreSQL

Run PGAdmin
Open the db (with password)
Open a query window
C/P or type in your query
Hit Run or F8



Alternatively, don't bother and wait for Holdem Manager (and/or PT3).