| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | FBaron(at)co(dot)belcorp(dot)biz |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: VACUUM with a small table too much delayed. |
| Date: | 2005-04-20 23:30:37 |
| Message-ID: | 2119.1114039837@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
FBaron(at)co(dot)belcorp(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nuno Souto | 2005-04-21 00:48:35 | PostgreSQL (real and effective user ids must match) error |
| Previous Message | FBaron | 2005-04-20 21:26:40 | VACUUM with a small table too much delayed. |