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 21028.1204255565@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>)
Responses Re: Batch update of indexes on data loading  ("Markus Bertheau" <mbertheau.pg@googlemail.com>)
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:
> BTW, why REINDEX requires access exclusive lock? Read-only queries
> are forbidden during the operation now, but I feel they are ok
> because REINDEX only reads existing tuples. 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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: A couple of PG schedule reminders
Next
From: Tom Lane
Date:
Subject: Re: CREATE TABLE, load and freezing