Forum OpenACS Development: Re: Duplicate keys on assessment

Forum OpenACS Development: Re: Duplicate keys on assessment - possible CR bug

34: Re: Duplicate keys on assessment - possible CR bug (response to 1)

Posted by Dave Bauer on 04/14/07 01:08 AM

Rocael

The new code is better and uses a function instead of the cr_dummy table. I don't see any reason to revert it. Luckily we were able to fix it by using new features in PG 8 what were not available in PG 7.

35: Re: Duplicate keys on assessment - possible CR bug (response to 34)

Posted by Richard Hamilton on 04/14/07 01:00 PM

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