VACUUM with a small table too much delayed.

Hi, I'm running a vaccum process to a table with 1427 records and three
indexes with the same size. This process is running 6 hours ago and does
not finish, I had to kill it.
I did the same to a table with 300.000 records and two indexes . and it
finished 20 minutes later.

What can it be happening with the first table?


This is the VACUUM message after cancel
INFO: --Relation public.unical_ejitem--
INFO: Pages 416: Changed 0, reaped 396, Empty 0, New 0; Tup 1427: Vac
20993, Keep/VTL 0/0, UnUsed 0, MinLen 130, MaxLen 150; Re-using:
Free/Avail. Space 3102472/3101520; EndEmpty/Avail. Pages 0/397.
CPU 0.02s/0.00u sec elapsed 3.48 sec.


Thanks for your help.

Fabio Bar=F3n S.
DBA, Plataforma Tecnologica
Gerencia Corporativa de Tecnologia
Tel : 4-37-61-61 Ext. 5123
Cel : 311 2-54-74-00


Aviso de confidencialidad:
Este mensaje de correo electr=F3nico contiene informaci=F3n estrictamente
confidencial no susceptible de ser distribuida. Si usted no es el
destinatario de este mensaje, por favor no publicarlo, copiarlo o tomar
cualquier otro tipo de accion sobre esta transmision. Si recibio este
mensaje por error, por favor notifiquenoslo y eliminelo lo antes posible.

Warning of confidentiality:
This message of electronic mail contains strictly confidential information
nonsusceptible to be distributed. If you are not the adressee of this
message, please do not publish it, copy it or take any other kind of action
on this transmission. If you got this message by mistake, please notify it
to us and eliminate it as soon as possible.


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Re: VACUUM with a small table too much delayed.

FBaron@co.belcorp.biz writes:
> Hi, I'm running a vaccum process to a table with 1427 records and three
> indexes with the same size. This process is running 6 hours ago and does
> not finish, I had to kill it.

Was it actually *doing* anything, or just sitting? Perhaps it was
waiting for some other process's lock.

> This is the VACUUM message after cancel
> INFO: --Relation public.unical_ejitem--
> INFO: Pages 416: Changed 0, reaped 396, Empty 0, New 0; Tup 1427: Vac
> 20993, Keep/VTL 0/0, UnUsed 0, MinLen 130, MaxLen 150; Re-using:
> Free/Avail. Space 3102472/3101520; EndEmpty/Avail. Pages 0/397.
> CPU 0.02s/0.00u sec elapsed 3.48 sec.

Hmm ... VACUUM hasn't printed messages that looked like that since 7.3
.... you might want to think about an update sometime.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend