Hi Steve,<br><br>Unfortunatelly I have no chance to test that patch now.<br>Slony was used as a temporary solution to migrate db cluster between 9.0 and 9.1.<br>And after that process were done, cluster returned to use hot-standby again.<br>
Sorry.<br><br>Kind Regards,<br>Maksym<br><br><div class="gmail_quote">On Sat, Dec 10, 2011 at 3:58 AM, Steve Singer <span dir="ltr"><<a href="mailto:ssinger@ca.afilias.info">ssinger@ca.afilias.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On 11-11-23 04:09 PM, Steve Singer wrote:<br>
<br>
Maxim,<br>
<br>
Did you ever check to see if this patch actually fixes your problem with running Slony against 9.1.x?<br>
<br>
Did you encounter any other issues with it?<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11-11-23 09:27 AM, Simon Riggs wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Nov 23, 2011 at 1:51 PM, Steve Singer<<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a><u></u>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11-11-23 04:28 AM, Simon Riggs wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Tue, Nov 22, 2011 at 10:26 PM, Steve Singer<<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a><u></u>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 11-11-20 05:47 AM, Cédric Villemain wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
</blockquote></blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
ISTM that setting the remote worker to REPEATABLE READ would work well<br>
for this case. Patch attached.<br>
<br>
</blockquote>
<br>
Simon, Did you forget to attach the patch? I don't see it.<br>
</blockquote>
<br>
Looks that way.<br>
<br>
</blockquote>
<br>
Thanks for the patch.<br>
<br>
So why would a SERIALIZABLE READ ONLY DEFERRED transaction produce fewer<br>
conflicts than a READ COMMITTED transaction? Currently the<br>
remote_listener gets the default isolation level (READ COMMITTED).<br>
<br>
The attached patch combines your two patches plus performs the same<br>
change to other places in remote_worker (there are places in<br>
remote_worker.c where that initial transaction is rolledback and<br>
restarted, this version also makes sure that those transactions are<br>
started as READ COMMITTED). It also makes the connections that the<br>
remote helpers do to the remote database for querying sl_log_x READ ONLY<br>
DEFERRED.<br>
<br>
When I run this patch through the test suite on 9.1 I don't see any<br>
serialization pivot failures (at least not yet).<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Maxim Boguk<br>Senior Postgresql DBA.<br><br>Phone RU: +7 910 405 4718<br>Phone AU: +61 45 218 5678<br><br>Skype: maxim.boguk<br>Jabber: <a href="mailto:maxim.boguk@gmail.com" target="_blank">maxim.boguk@gmail.com</a><br>
<br>LinkedIn profile: <a href="http://nz.linkedin.com/in/maximboguk" target="_blank">http://nz.linkedin.com/in/maximboguk</a><br>If they can send one man to the moon... why can't they send them all?<br><br>МойКруг: <a href="http://mboguk.moikrug.ru/" target="_blank">http://mboguk.moikrug.ru/</a><br>
Сила солому ломит, но не все в нашей жизни - солома, да и сила далеко не все.<br>