Database vacuum strange behaviour

[darklingroom]

Recently I imported a huge amount of hands (1 mln) then purged it saving only 2000 hands and then made db compression via HM (method: Full). After about 20 minutes it showed me smthng about that: "Error - operation cancelled by user". First of, I'm sure I didn't cancel it but even if I accidently did, why is it called "error"?

Then I went to pgAdmin III and made the same (vacuum + analyze, then reindex), everything went fine but suprisingly quick: about 20 min for vacuum + analyze and 5 min for reindex. My notebook is not that cool, so I was expecting to wait for a night or something. For example the importing of the hands took more than 6 hours. So, there is a report about HM error and a question: is everything went fine? It looks like that, but in a very unexpected way.

[B-Money]

Sounds like it timed out for some reason.

Is your postgres on a different hard drive or not installed in the default location?

If the PGAdmin console finished it, I guess you are good to go though???

[darklingroom]

I have only one harddrive, everything's default. HM ver 1.11.04 btw, Postgres 8.4.4. Yea, I guess it's ok, just wanted to reinsure myself