Now that it has been established that the Postgres bug that caused this issue has been fixed in PG 8.2.x, there is one thing that is not clear to me from the posts above:
Does the currently committed new code include the explicit locking proposed by Rocael (LOCK TABLE acs_objects IN SHARE ROW EXCLUSIVE MODE;)?
If so, someone mentioned that this may undermine MVCC in some cases. Is this correct and if so are we sure that the new code is as good as it can be for PG versions 8.2.x and later?
Regards
RIchard
