On 4/25/06 12:24 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote: > I'm inclined to think that the right solution is to fix UpdateStats and > setRelhasindex so that they don't use simple_heap_update, but call > heap_update directly and cope with HeapTupleUpdated (by looping around > and trying the update from scratch).
Is there a verdict on what can/should/will be done for this? As far as I can tell from all this, there appears to be no workaround (even kludgy) other than to not build indexes in parallel - not an attractive option. If I'm only building two indexes simultaneously, what would happen if I tried to lock pg_class in the shorter index build transaction? Besides seeming like a bad idea... Wes ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
