Vacumming and Analyzing

[KronosUVA]

I attempt to Vacuum my huge database, but then there is an error. I am running 64-bit Vista and have turned off UAC.

I followed the directions to do the manual Vacuum, but it doesn't last nearly long enough and doesn't appear to be doing much.

Is there any way to make it so the program can do the correct vacuuming within holdemmanager?

Would I have to make a brand new database and import all the hands and then try vacuuming?

[morny]

Can you copy and paste the text it produces in that window when its finished please

[KronosUVA]

I went back a good ways in the window. Hope this helps.

This was probably the 7th time I've done it, but even the first time it only took a short amount of time. No way it takes only that long with the amount of hands in the database.

Thank you for your help!



INFO: "postflopactions_month": moved 12018 row versions, truncated 28146 to 27912 pages
DETAIL: CPU 1.54s/1.66u sec elapsed 78.37 sec.
INFO: index "postflopactions_month_idx1" now contains 1593815 row versions in 6509 pages
DETAIL: 12018 index row versions were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.07s/0.04u sec elapsed 0.19 sec.
INFO: analyzing "public.postflopactions_month"
INFO: "postflopactions_month": scanned 3000 of 27912 pages, containing 171283 live rows and 0 dead rows; 3000 rows in sample, 1593617 estimated total rows
INFO: free space map contains 3580 pages in 64 relations
DETAIL: A total of 4496 page slots are in use (including overhead).
4496 page slots are required to track all free space.
Current limits are: 204800 page slots, 1000 relations, using 1269 kB.

Total query runtime: 484453 ms.

[morny]

Can you try creating a new database, import a small amount of hands, vacuum that new database and post the text it displays for that

It looks likely theres something wrong with the database and it will need to be exported and reimported into a new one but check that first

[KronosUVA]

Sorry for the delay. However, I made another DB and it again failed to perform the task within the program. Here is the last X text when I do it manually in PGadmin 8.3.

There were 0 unused item pointers.
Total free space (including removable row versions) is 0 bytes.
0 pages are or will become empty, including 0 at the end of the table.
0 pages containing 0 free bytes are potential move destinations.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: index "pokerhands_hero_pkey" now contains 0 row versions in 1 pages
DETAIL: 0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: index "pokerhands_hero_idx1" now contains 0 row versions in 1 pages
DETAIL: 0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: analyzing "public.pokerhands_hero"
INFO: "pokerhands_hero": scanned 0 of 0 pages, containing 0 live rows and 0 dead rows; 0 rows in sample, 0 estimated total rows
INFO: free space map contains 37 pages in 129 relations
DETAIL: A total of 2064 page slots are in use (including overhead).
2064 page slots are required to track all free space.
Current limits are: 204800 page slots, 1000 relations, using 1269 kB.

Total query runtime: 674 ms.


Thank you for your time.

Should I be reinstalling the program or something?

[morny]

Are you sure your copying all the data in that windown, try putting the mouse pointer beside the text and pressing CTRL+A

it looks like its completing the process but usually it should start with

INFO: vacuuming "information_schema.sql_features"INFO: "sql_features": found 0 removable, 494 nonremovable row versions in 5 pages
DETAIL: 0 dead row versions cannot be removed yet.
Nonremovable row versions range from 42 to 187 bytes long.
There were 0 unused item pointers.


So it looks like your missing some of the text

[KronosUVA]

The whole report even for the small database is far too large to put in a post. Can I email it to you?

[morny]

Ah well if its that big then it was succesful, once you get that message total query took x ms then it was successful

[KronosUVA]

So that means that the right thing to do is export hands then import all them into a new DB? Then vacuum?

[morny]

You dont have to create a new database to vacuum but you may need to do this if theres a problem with the original database, normally youd just vacuum every week or 2 depending on performance.