Open Stack

> But the isolation mode change won’t really help here as pointed out by
Jay; discrete transactions have to be used instead.
I still think it will, per postgres documentation (which might look
confusing, but still...)
It actually helps for mysql, that was confirmed. For postgres it appears to
be the same.

Thanks,
Eugene.

On Thu, Nov 20, 2014 at 12:56 AM, Mike Bayer <mbayer at redhat.com> wrote:

>
> > On Nov 19, 2014, at 4:14 PM, Clint Byrum <clint at fewbar.com> wrote:
> >
> >
> > One simply cannot rely on multi-statement transactions to always succeed.
>
> agree, but the thing you want is that the transaction either succeeds or
> explicitly fails, the latter hopefully in such a way that a retry can be
> added which has a chance at succeeding, if needed.  We have transaction
> replay logic in place in nova for example based on known failure conditions
> like concurrency exceptions, and this replay logic works, because it starts
> a new transaction.   In this specific case, since it’s looping within a
> transaction where the data won’t change, it’ll never succeed, and the retry
> mechanism is useless.   But the isolation mode change won’t really help
> here as pointed out by Jay; discrete transactions have to be used instead.
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141120/73def939/attachment.html>