From: Sander Steffann <sander@steffann.nl>
To: Kristian Eide <kreide@online.no>
To: Ken Corey <ken@kencorey.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: VACUUM not doing its job?
Date: Sun, 4 Aug 2002 00:59:51 +0200
Message-ID: <001201c23b41$799a8d00$64c8a8c0@balefire10ww> (raw)
References: <035d01c23b2f$c5d49420$6b97f181@speed>
<1028412884.28635.22.camel@kenlinux.bithub.org>
<037901c23b3e$d542a140$6b97f181@speed>
> This is not good as the database is in use 24/7, and without the indexes
> everything comes to a screeching halt. This means I probably will have to
> stop the programs using the database for the time it takes to re-create
the
> indexes; this is better than having to dump/restore everything however :)
You can try using REINDEX instead of dropping and creating the index. It
takes an exclusive lock on the table (instead of a write-lock during CREATE
INDEX) so your application will have to wait during reindex, but maybe it is
faster... When you use the reindexdb script in the contrib dir you can even
put it in a crontab.
Sander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sander@steffann.nl, kreide@online.no, ken@kencorey.com
Subject: Re: VACUUM not doing its job?
In-Reply-To: <001201c23b41$799a8d00$64c8a8c0@balefire10ww>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox