PokerTracker

I noticed that after i get done housekeeping and close PT3, postgres is still using up tons of memory. I have mine 'optimized per PT3 suggestions' too so it takes up even more.

So after a housekeeping and with PT3 still open i have 10 processes of postgres.exe running. After i close PT3 i have 6 postgres.exe's running, which one of them is tying up 1GB of RAM. The others are fairly small with one using 27MB, and the 4 others using 5MB each. Why doesn't that one process using 1GB free up after i close PT3?

Seems to be a memory leak because 4/10 processes of postgres disappear after closing PT3 and 5/10 are pretty much reduced to nothing, but there is that one process that stays at 1GB. As a temporary fix to this problem, am i able to end this process with no side effects? Currently i have just been re-starting my computer after a housekeeping.

What do you guys think?

There will always be multiple processes - that's how postgres works. Those 6 will always be there - I can't remember off the top of my head what they are, but they are standard.

WhiteRider wrote:There will always be multiple processes - that's how postgres works. Those 6 will always be there - I can't remember off the top of my head what they are, but they are standard.

I think you missed the point. One of those processes is taking up 1GB of RAM after i close PT3. The others drop...not the 1GB process. Look into this

When you close PT3 all PT3 specific processes in PostgreSQL are shut down.

If there's a memory leak in PostgreSQL itself you'll need to talk to the PostgreSQL developers -- we don't write that software.

kraada wrote:If there's a memory leak in PostgreSQL itself you'll need to talk to the PostgreSQL developers -- we don't write that software.

You may not write that software but your program relies on it to work. Just thought you guys would be concerned. Can you at least answer my initial question?


"......am i able to end this process with no side effects?" (after i close PT3)

Yes, though you should end the process gracefully by clicking Start --> Programs --> PostgreSQL --> Stop Services, rather than just ending the task in Task manager.

From another semi-related Post:

kraada wrote:As I said in the other thread, that's something you'll have to take up with the PostgreSQL people; I can't reproduce that memory leak myself, or I'd talk to them about it.

I know some where out there someone will read this and care. Be it someone from PostgreSQL or some random smart PT user. If you want to reproduce this:

1. First optimize your postgreSQL for 4GB of RAM(Must have 4GB RAM* to reproduce my problem, but who doesnt now-a-days).
2. Then get a data-base of roughly 8.5Million hands(This is how many i had at the time, though i remember similiar 1GB memory leak with less hands).
3. Now run a Housekeeping-Cluster(This will take a few hours.....see viewtopic.php?f=15&t=14898).
4. Afterwards exit PT3.
5. Then notice one process of postgres.exe using 1GB of RAM still.

*Windows XP Pro SP3

There you go Kraada...reproduce it and talk to them about it