Обсуждение: vacuum taking long time

Поиск
Список
Период
Сортировка

vacuum taking long time

От
Dale Walker
Дата:
I have a machine inadvertently reboot on me this morning, and I have
been running a vacuumdb command to try and check it.

The vacuum command has processed the indexes OK, but it hasn't returned
to a prompt as yet (3hrs)

The table has only taken about 5min to do a vacuum on in the past... any
suggestions??


This is what I have on my screen so far...
------------------------------------------------------------------
$ vacuumdb --dbname=icr --table=log --verbose --echo
VACUUM VERBOSE  log
NOTICE:  --Relation log--
NOTICE:  Pages 17010: Changed 0, reaped 890, Empty 0, New 0; Tup
1031544: Vac 56920, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 114, MaxLen
126; Re-using: Free/Avail. Space 7048436/7048436; EndEmpty/Avail. Pages
0/890. CPU 1.95s/0.51u sec.
NOTICE:  Index idx_lacctterminatecause: Pages 2049; Tuples 1031544:
Deleted 963. CPU 0.26s/1.76u sec.
NOTICE:  Index idx_lservicetype: Pages 2047; Tuples 1031544: Deleted
963. CPU 0.30s/1.71u sec.
NOTICE:  Index idx_lnasporttype: Pages 2047; Tuples 1031544: Deleted
962. CPU 0.30s/1.70u sec.
NOTICE:  Index idx_lnasport: Pages 2594; Tuples 1031544: Deleted 962.
CPU 0.36s/1.72u sec.
NOTICE:  Index idx_lnasip: Pages 3595; Tuples 1031544: Deleted 962. CPU
0.39s/1.82u sec.
NOTICE:  Index idx_luser: Pages 3303; Tuples 1031544: Deleted 962. CPU
0.33s/1.90u sec.
NOTICE:  Index idx_loutdate: Pages 2569; Tuples 1031544: Deleted 962.
CPU 0.35s/1.72u sec.
NOTICE:  Index log_pkey: Pages 2173; Tuples 1031544: Deleted 962. CPU
0.27s/1.75u sec.

-----------------------------------------------------------------------------------




--
Dale Walker                                              dale@icr.com.au
Independent Computer Retailers (ICR)               http://www.icr.com.au
ICRnet                               http://www.icr.net.au

Re: vacuum taking long time

От
Dale Walker
Дата:
Dale Walker wrote:
>
> I have a machine inadvertently reboot on me this morning, and I have
> been running a vacuumdb command to try and check it.
>
> The vacuum command has processed the indexes OK, but it hasn't returned
> to a prompt as yet (3hrs)
>
> The table has only taken about 5min to do a vacuum on in the past... any
> suggestions??
>
> This is what I have on my screen so far...
> ------------------------------------------------------------------
<snipped>


I just bombed out 'postmaster' with a kill -9 , restarted and I'm in the
process of doing a pg_dump of the table.

I'll then drop the table, and re-create from the dump...


Should be OK??

The table was only created from radius log files anyway, so I can
recreate if I need to...

Anyone have any suggestions as too where I should start looking for what
went wrong??


--
Dale Walker                                              dale@icr.com.au
Independent Computer Retailers (ICR)               http://www.icr.com.au
ICRnet                               http://www.icr.net.au