Quote:
Originally Posted by _dave_
level of logging detail and all manner of other options are found in the file postgresql.conf, changes require restart of postgres server to take effect. where it puts the log files is specified in there too I think. The postgresql.conf file is pretty well commented IIRC, more docs here: http://www.postgresql.org/docs/9.1/s...g-logging.html - the parameter we're probably most interested in is is this one, we want "all":
have to read more but seems great, expecially if I can see all the events when I create a new player.
Quote:
Also, the easy way to get only HU players is to only import HU games into a fresh database, ldo. It's perhaps unwise to experiment with SQL commands including UPDATEs and INSERTSs on your main, only, all-time database lol.
Yes, I have different databases, but could be right to select all players that played heads up. However, I think that he selects only 2 max, but tends to exclude MTT heads up.
@genher
I have 11k players on my db, so I don't think this is the problem. But well, you can divide the player into 2 (or more) groups and then insert a group at time.
For example, you can add at the end of the code
Code:
[...]
AND p1.pokersite_id <> -1
AND p1.player_id < 4000
In the next query instead
Code:
AND p1.player_id >= 4000 AND p1.player_id < 8000
and so on.
@benjamin I have very little time to experiment with PT4 cause university exam so your help is very appreciated
And yes, make a backup if you are experimenting and have no idea of SQL