On sön, 2012-07-01 at 01:56 +0000, Steve Singer wrote: > The problem is that slony 2.0.x (slon) opens up serializable > transactions that caues the conflicts. This can happen even if user > applications only perform repeatable read transactions. The > transactions will be retried after they are aborted so they should > eventually get through.
OK, that's more serious then. I'll see what I can do. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
