Is it feasible to add a "reindex concurrently" that doesn't lock the
table for the rebuild, then locks the table when doing a second pass to
pickup rows that were changed after the first pass? Or something like
that....
On Fri, 19 Jan 2007 12:45:03 -0500, "Tom Lane" <tgl@sss.pgh.pa.us> said:
> "Ed L." <pgsql@bluepolka.net> writes:
> > Online index creation definitely helps us toward 24x7. But
> > wouldn't we still have to drop the old index, thus blocking
> > production queries?
>
> Yes, but only for a very short period.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
