Simon Riggs wrote:
On Wed, 2007-07-11 at 16:49 -0700, Joe Conway wrote:
On cvs head, I can get "tuple concurrently updated" if two separate
transactions are both trying to drop the same index:
ERROR: tuple concurrently updated
The reason I ask is that someone contacted me who is seeing this on a
production system, and the abort on session #2 is rolling back a large
bulkload.
This situation will always cause an error on session #2, since if you
lock this more closely you'll get an ERROR because the object does not
exist.
That's a really good point. In any case I had already asked them to look
into moving the index related DDL outside the data loading transaction.
Thanks,
Joe
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
