Re: Problem with VACUUM after very large delete?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Doug Fields <dfields-pg-general(at)pexicom(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with VACUUM after very large delete?
Date: 2002-12-17 23:32:36
Message-ID: 17547.1040167956@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Doug Fields <dfields-pg-general(at)pexicom(dot)com> writes:
> Earlier today I deleted about 31 million records from one of our tables
> with a very complex query which required a full table scan. This query took
> quite a few hours to run (in fact, overnight).

> Why? The VACUUM doesn't seem to be vacuuming the two indexes on the table.

Have you got any open transactions hanging about? VACUUM probably
thinks it can't remove the tuples yet because they're still potentially
visible to somebody under MVCC rules.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Luke Van 2002-12-17 23:50:37 test--please disregard
Previous Message Doug Fields 2002-12-17 23:31:22 Re: Problem with VACUUM after very large delete?