Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group