Re: vacuum is not sufficient? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: vacuum is not sufficient?
Date
Msg-id 29458.1060372587@sss.pgh.pa.us
Whole thread Raw
In response to vacuum is not sufficient?  (Matteo <sgala@sgala.com>)
List pgsql-bugs
Matteo <sgala@sgala.com> writes:
> INFO:  --Relation public.active_sessions_split--
> INFO:  Index active_sessions_split_pkey: Pages 91838; Tuples 5381: Deleted 31.
>         CPU 4.26s/0.47u sec elapsed 135.47 sec.
> INFO:  Index k_asp_changed: Pages 46192; Tuples 5381: Deleted 31.
>         CPU 2.32s/0.25u sec elapsed 34.94 sec.
> INFO:  Removed 31 tuples in 6 pages.
>         CPU 0.00s/0.00u sec elapsed 0.01 sec.
> INFO:  Pages 78376: Changed 4, Empty 0; Tup 5381: Vac 31, Keep 0, UnUsed 615471.
> Total CPU 9.93s/1.13u sec elapsed 186.68 sec.

I'd try a dump/reload or CLUSTER to get the table back down to a
reasonable size.  In future, try vacuuming it more often.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Silvio Scarpati
Date:
Subject: Re: UNION discards indentical rows in postgres 7.3.3
Next
From: Bruce Momjian
Date:
Subject: Re: ALTER TABLE table RENAME TO sould change also sequence name