Purging all (and only) observed hands from a DB?

[Fuzzydunflop]

Do I simply click 'Only observed hands' and nothing else and click purge?

[WhiteRider]

Yes, but make sure your name is shown. See the Tutorial: Purging Sessions for more info.

[Fuzzydunflop]

Everytime I start a purge, it goes to the 'Not Responding' windows thing and no Purge Status Bar shows up at all.

Is this normal? Is it doing the purge? Or should I be seeing a status window?

[WhiteRider]

You should see a status window, but it may not appear for a while.
If you have a large database or are purging a lot of hands it will take some time so let it run for a while.
Enable logging and restart PT3 and run the purge overnight or something and if you still don't see any progress then attach the PokerTracker3.log file to a Support ticket so that we can investigate.
Tutorial: Submitting a Bug Report

[rowhousepd]

I didn't used to have problems w/ purges freezing or going at a ridiculously slow pace, but I do now -- right after the last build. Is anyone else complaining about database maintenance issues since the update? I've purged observed hands before roughly the same sized db's, but it's definitely a whole other league of slowness nowadays. Lemme know. Thanks.

[kraada]

I haven't heard of any other complaints of purging slowdowns myself.

[rowhousepd]

Tell me if this seems weird:

I manually imported all of my observed into the wrong database other day. The db in question had only about ~62k real hands (played by me) into which I mistakenly imported ~1.1 million. (Yikes!) I ran housekeeping, selected purge, clicked observed hands, it started running it, and I went to bed. 8 hours later it was still running and estimated that there was 9000+ hours to go. I canceled the purge, ran housekeeping again, and to my surprise saw that the db had a total of 1.0 million remaining. It wiped a mere ~100k over the course of 8 hrs.

I’m running PT3 v3.06.2, postgres 8.4, my computer is a perfectly capable, smooth-running machine (2.4 Ghz, 8 GB ram, Windows 7, 64-bit) that's never had a real problem like this w/ db maintenance before. Does this sound way off ... 8 hrs to wipe 100k hands?

[vicnice]

Tell me if this seems weird:

I manually imported all of my observed into the wrong database other day. The db in question had only about ~62k real hands (played by me) into which I mistakenly imported ~1.1 million. (Yikes!) I ran housekeeping, selected purge, clicked observed hands, it started running it, and I went to bed. 8 hours later it was still running and estimated that there was 9000+ hours to go. I canceled the purge, ran housekeeping again, and to my surprise saw that the db had a total of 1.0 million remaining. It wiped a mere ~100k over the course of 8 hrs.

I’m running PT3 v3.06.2, postgres 8.4, my computer is a perfectly capable, smooth-running machine (2.4 Ghz, 8 GB ram, Windows 7, 64-bit) that's never had a real problem like this w/ db maintenance before. Does this sound way off ... 8 hrs to wipe 100k hands?

Unfortunately purging is ridiculously slow (kraada and whiterider would know more specific numbers, but yeah, it is very slow on large databases). I think it is because when it is purging it has to delete things from a lot of locations in order to make sure the data remains consistent.

It might just be faster for you to create a new database, and import those 62k hands into the new one and just delete the old one.

[kraada]

Reimporting 62k hands into a new database will be far, far faster than purging a million hands from any database.

[rowhousepd]

Yup, that's what I'm doing now and it's going ok. I just hope I never really have to purge something down the road.