Re: Tricky bugs in concurrent index build

> > Is it not possible to brute force this adding an AM method to insert

> > without the uniqueness check?
> 
> Hm.  Actually there already is a feature of aminsert to allow 
> suppressing the unique check, but I'm not sure whether using 
> it for RECENTLY_DEAD tuples helps.  Seems like we have to 
> wait to see whether DELETE_IN_PROGRESS deleters commit in any case.

Um, but if we wait for the DELETE_IN_PROGRESS tuple, after the wait we
can
add it eighter with or without the unique check (depending on
commit/abort).

Then at least we don't need to wait in a 3rd pass for readers ?

Andreas