I have an IO congested database (PostgreSQL 7.2) with too many
(overlapping) indexes, so the obvious solution is to drop them.
DROP INDEX seems to want to take several minutes to complete, which
causes a backup of clients and me to eventually abort the process to let
all the backed up queries go through.
The real question is why does DROP INDEX take more than a couple of
seconds to complete? It is not held up by locked. The indexes are about
5GB in size. I assume PostgreSQL is trying to read the entire index off
disk prior to removal or something equally strange. Is this necessary?
pgsql-hackers by date
|Next:||From: markw||Date: 2004-02-16 17:18:11|
|Subject: Re: Proposed Query Planner TODO items |
|Previous:||From: markw||Date: 2004-02-16 16:26:53|
|Subject: Re: Proposed Query Planner TODO items|