Re: Batch update of indexes on data loading - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Batch update of indexes on data loading
Date
Msg-id 23260.1204267068@sss.pgh.pa.us
Whole thread Raw
In response to Re: Batch update of indexes on data loading  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Can we do REINDEX
>>> holding only shared lock on the index?
>> 
>> No.  When you commit the reindex, the old copy of the index will
>> instantaneously disappear; it will not do for someone to be actively
>> scanning that copy.

> Hmm... Is it ok if the index will *not* instantaneously disappear?

It's not impossible but I really question whether it'd be worth the
complexity.  There was something very closely related just yesterday
about whether DROP INDEX has to take exclusive lock ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Re: Batch update of indexes on data loading
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables