X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 658DE52849 for ; Tue, 21 Jun 2005 16:45:17 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 89992-07 for ; Tue, 21 Jun 2005 19:45:15 +0000 (GMT) Received: from lynet.oppetid.no (oppetid.no [80.65.51.2]) by svr1.postgresql.org (Postfix) with ESMTP id CF2C952847 for ; Tue, 21 Jun 2005 16:45:14 -0300 (ADT) Received: by lynet.oppetid.no (Postfix, from userid 1019) id 9E56C11A2E7; Tue, 21 Jun 2005 21:46:39 +0200 (CEST) Date: Tue, 21 Jun 2005 21:46:39 +0200 From: Tobias Brox To: John A Meinel Cc: Yves Vindevogel , pgsql-performance@postgresql.org Subject: Re: Limit clause not using index Message-ID: <20050621194639.GG22746@oppetid.no> References: <42B8275C.8040300@arbash-meinel.com> <7e514564b9a159480857de53cc1764fd@implements.be> <42B82ED0.1010009@arbash-meinel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42B82ED0.1010009@arbash-meinel.com> Organization: Group Nordicbet User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/408 X-Sequence-Number: 13045 [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