Re: VACUUM with a small table too much delayed. - Mailing list pgsql-admin

From Tom Lane
Subject Re: VACUUM with a small table too much delayed.
Date
Msg-id 2119.1114039837@sss.pgh.pa.us
Whole thread Raw
In response to VACUUM with a small table too much delayed.  (FBaron@co.belcorp.biz)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: FBaron@co.belcorp.biz
Date:
Subject: VACUUM with a small table too much delayed.
Next
From: Enrico Weigelt
Date:
Subject: Re: cost of empty fields