From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Krowa Krowax <krowa333(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Vacuum Full - stops responding(?) |
Date: | 2009-10-20 02:37:40 |
Message-ID: | dcc563d10910191937ld71f44bif644e46e4acb3d94@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Oct 19, 2009 at 4:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Krowa Krowax <krowa333(at)gmail(dot)com> writes:
>> INFO: vacuuming "pg_toast.pg_toast_17929229"
>> INFO: "pg_toast_17929229": found 6203 removable, 257509 nonremovable
>> row versions in 20509016 pages
>> DETAIL: 0 dead row versions cannot be removed yet.
>> Nonremovable row versions range from 45 to 2030 bytes long.
>> There were 87521183 unused item pointers.
>> Total free space (including removable row versions) is 166910212580 bytes.
>> 20384082 pages are or will become empty, including 3 at the end of the table.
>> 20507826 pages containing 166910155528 free bytes are potential move
>> destinations.
>
> That might be about the worst case of table bloat I've ever seen :-(
>
>> After 10 hours nothing new appear... What is going on with this vacuum?
>
> It's trying to repack your table in place. On the whole, I'd suggest
> you cancel the vacuum and try a CLUSTER or some such instead.
Unless that table's already in (mostly) index order, even cluster is
gonna be pretty painful.
I'd suggest a dump and reload myself.
> After you get this cleaned up, think about enabling autovacuum ...
This. Very much this.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-10-20 03:46:10 | Re: Vacuum Full - stops responding(?) |
Previous Message | Tom Lane | 2009-10-19 22:38:44 | Re: Vacuum Full - stops responding(?) |