Message-Id: <s2b94874.032@gwmta.wicourts.gov>
Date: Tue, 21 Jun 2005 16:11:40 -0500
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: <john@arbash-meinel.com>, <tobias@nordicbet.com>
Cc: <yves.vindevogel@implements.be>,
	<pgsql-performance@postgresql.org>
Subject: Re: Limit clause not using index
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I just tried this on 8.0.3.  A query which runs very fast through an
index on a 25 million row table blocked when I dropped the index within
a database transaction.  As soon as I rolled back the database
transactiton, the query completed, the index appears fine, and the query
runs fast, as usual.
 
So, it looks like this is right except for the assertion that the index
is still available for other queries.
 
-Kevin
 
 
>>> Tobias Brox <tobias@nordicbet.com> 06/21/05 2:46 PM >>>
[John A Meinel - Tue at 10:14:24AM -0500]
> I believe if you drop the indexes inside a transaction, they will
still
> be there for other queries, and if you rollback instead of commit, you
> won't lose anything.

Has anyone tested this?

(sorry, I only have the production database to play with at the moment,
and I don't think I should play with it ;-)

-- 
Tobias Brox, Beijing


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly