From: Tobias Brox <tobias@nordicbet.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: John A Meinel <john@arbash-meinel.com>
Cc: Yves Vindevogel <yves.vindevogel@implements.be>
Cc: pgsql-performance@postgresql.org
Subject: Re: Limit clause not using index
Date: Wed, 22 Jun 2005 11:54:55 +0800
Message-ID: <20050622035455.GP7839@tobias> (raw)
In-Reply-To: <17468.1119388807@sss.pgh.pa.us>
References: <d0da86521cd54473cac40df63bb14546@implements.be>
<42B8275C.8040300@arbash-meinel.com>
<7e514564b9a159480857de53cc1764fd@implements.be>
<42B82ED0.1010009@arbash-meinel.com>
<20050621194639.GG22746@oppetid.no>
<17468.1119388807@sss.pgh.pa.us>
[Tom Lane - Tue at 05:20:07PM -0400]
>
> Certainly. Bear in mind though that DROP INDEX will acquire exclusive
> lock on the index's table, so until you roll back, no other transaction
> will be able to touch the table at all. So the whole thing may be a
> nonstarter in a production database anyway :-(.
That's what I was afraid of. I was running psql at the production DB
without starting a transaction (bad habit, I know) and tried to drop an
index there, but I had to cancel the transaction, it took forever and
in the same time blocking all the revenue-generating activity.
--
Tobias Brox, +86-13521622905
Nordicbet, IT dept
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-performance@postgresql.org
Cc: tobias@nordicbet.com, tgl@sss.pgh.pa.us, john@arbash-meinel.com, yves.vindevogel@implements.be
Subject: Re: Limit clause not using index
In-Reply-To: <20050622035455.GP7839@tobias>
* 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