Hi Guys,



I encounter a problem when using slony. I had a transaction that updated
both table A and table B. This is atomic transaction. While slony is doing
the replication, on parent, the transaction is done, on slave node, there
might exists error which cause the transaction error. That=92s to say, on
slave node, table A is updated while table B is not updated. This will cause
problem to our application. Is there any way in slony to keep the
transaction atomic?



Thanks a lot

Han He
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20090826/=
8a405468/attachment.htm