Thanks, it's very likely your trouble is caused by the problematic version of PostgreSQL you're using however even if it turns out to not be, you do need to upgrade it and when logging again it would be best to do only what's necessary to capture the trouble (there appear to be many things going on in this log such as manual imports, running for hours, etc.).
So do this:
1. Turn off auto rate while playing since that can cause overhead with non-small databases which in turn can lead to other troubles. Auto rate also does not support tournament games meaning it can only hurt to have it running during them.
Click "Configure -> Auto Rate -> Criteria" and take the check mark out of "During..." at the bottom.
2. For some reason hand history files may not always be getting moved so with your poker software closed, check all your poker site hand history folders and move any files/folders found to "C:/Program Files/PokerTracker 3/Processed". The one I see in your log is this:
C:\Users\name\folder\username
Check this folder too:
C:\Users\name\foldername
When closing things down for the day or session, close your poker site software then stop PokerTracker3 auto import and close it last to make sure PokerTracker3 can move the files.
3. To upgrade PostgreSQL see this:
viewtopic.php?f=45&t=4098&p=149563p149563#p149563Follow all the steps. You'll be upgrading to a new 8.3 so if you find yourself installing 8.4 or 9.x, something's gone wrong so stop there and let me know.
When you do the housekeeping after, use "Vacuum", "Analyze" and "Rebuild cache" options.
4. After all this, close/start PokerTracker3 with logging enabled again and play only long enough to capture the original trouble.
I suspect it will not occur again but if it does send the new PokerTracker3 logs and these:
--> The *newest* 4 or 5 PostgreSQL logs (click on the "Date Modified" column to sort the files by date): PostgreSQL log files
Mike
by the other mike [PokerTracker Support]