Re: Slow VACUUM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wim <wdh(at)belbone(dot)be>
Cc: PgSQL Novice ML <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Slow VACUUM
Date: 2003-09-12 14:21:30
Message-ID: 10783.1063376490@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Wim <wdh(at)belbone(dot)be> writes:
> PS I created 4 indexes on the tables. I cannot cancel the query... It
> keeps running. Otherwise I thought of dropping the indexes, vacuum the
> table and re-create the indexes...

Sure you can cancel it (assuming you're running any remotely up-to-date
version of Postgres). If you didn't issue the vacuum command from an
interactive psql, the easiest way is to identify the backend running the
command and send it a SIGINT ("kill -INT pid-of-backend"). Be sure to
use SIGINT and not any other signal.

If what you're trying to do is a VACUUM FULL, dropping the indexes
should help. Plain VACUUM I'm not so sure is worth the trouble.

Also you might try increasing VACUUM_MEM setting before you try again.

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Steve Bond 2003-09-12 14:50:32 Error: The database does not exist on the server
Previous Message Tom Lane 2003-09-12 14:13:50 Re: Finding connected users