<div dir="ltr"><div>Thank you Tatsuo,<br><br></div>What solution is there for implementing HA in such a scenario? Threaded requests, to threaded client connections, to a master/slave replication system. Would I have to use pgpool's Replication Mode and ditch the Slony approach?<br><div><div><div class="gmail_extra"><br clear="all"><div>--Cal<br><br></div><div><a href="mailto:cal@fbsdata.com" target="_blank"></a></div>
<br><div class="gmail_quote">On Thu, Oct 16, 2014 at 6:06 PM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">> Hi everyone,<br>
><br>
> I have encountered a problem with pgpool using Slony for replication to<br>
> slaves. The client to pgpool in my case is an API, so requests come in<br>
> concurrently on independent connections. If we have an insert directly<br>
> followed by a select for that record, the select is load balanced between<br>
> the master and slave, resulting in a 50% chance of a failure. Since the<br>
> select ends up coming from a separate httpd child process, there is no way<br>
> to keep the insert and select in the same transaction.<br>
><br>
> Am I missing something in the documentation and configs? Can pgpool<br>
> intelligently recognize specific records that have been inserted to a<br>
> table, then direct all selects for that record to the master until Slony<br>
> has replicated it to the slaves?<br>
<br>
</div></div>No. That's the limitaion of Slony (more presicely, asynchronous<br>
replication systems include streaming replication).<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div><br></div></div></div></div>