Skip site navigation (1) Skip section navigation (2)

Re: Batch update of indexes on data loading

From: "Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Batch update of indexes on data loading
Date: 2008-02-29 04:40:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
2008/2/29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)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.

Can a shared lock be taken at first, and when the new index is ready,
in order to delete the old index, elevate that lock to an exclusive


Markus Bertheau

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-02-29 05:05:45
Subject: Re: Batch update of indexes on data loading
Previous:From: Andrew DunstanDate: 2008-02-29 04:29:01
Subject: Re: Silly Newbie question

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group