From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Andy Chambers <achambers(at)mcna(dot)net> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: dropping an index inside a transaction |
Date: | 2012-03-18 03:21:46 |
Message-ID: | CAOR=d=2BzTcr7Zgv7oyig9VM1ajhijLWD7-kgvbz_wBveG30EQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Mar 17, 2012 at 8:37 PM, Andy Chambers <achambers(at)mcna(dot)net> wrote:
> Hi All,
>
> If one drops an index inside a transaction, is that index still usable
> by other transactions? My use-case is loading millions of records
> into a heavily indexed table. I'd like to speed up the load by
> temporarily dropping the indices. I'm wondering if I can do this
> inside a transaction so that the rest of the application can still
> benefit from the indices.
If another transaction is already relying on the index you can't drop
it. Once you drop it in a transaction all other queries against the
tables will be waiting behind the exclusive lock on the transaction to
finish to access the table.
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2012-03-18 04:57:37 | Re: why no create variable |
Previous Message | Scott Marlowe | 2012-03-18 03:20:00 | Re: dropping an index inside a transaction |