Re: BUG #1333: vacuum full apparently fails to complete

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Keith Halewood" <keith_halewood(at)systems-intelligence(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1333: vacuum full apparently fails to complete
Date: 2004-11-30 16:40:23
Message-ID: 21194.1101832823@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> At this point, the vacuum is *still* in progress (after 8 hours) and disc
> activity is exclusively the result of this vacuum, about 140 blocks/second
> with no disc queues. Is this likely to be a bug or just a scalability issue
> involving vacuum and the large object table?

vacuum full can take an awfully long time. It might be worth your while
to try a CLUSTER instead.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-11-30 16:53:09 Re: Out of memory while UPDATE some_table ... FROM some_view (8.0 beta5)
Previous Message Stephan Heilner 2004-11-30 15:52:19 service doesn't start