<div dir="ltr">We examined the native replication mode, but our other databases and aplications using OIDs, and random values, and I afraid we will be some problems. That reason we're staying in streaming replication mode , and we use OTRS without pool in the production area :(<br>
<br>Do you planning in the future releases some extra Load Balance parameters?<br>I'm thinking of for example white/black list to turn off/on it on the databases, tables, etc. <br><br>Thanks for your attention,<br>Csaba<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-04 9:13 GMT+02:00 Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">> We're testing it with your suggested 0 backend weight in the slave. It<br>
> working fine without load balancing mode.<br>
><br>
> We would like to steer clear of the replication lag problems, that reason<br>
> we're using synchronous replication with remote_write level settings. But<br>
> I see it is not enough.<br>
<br>
</div>No, it's not. PostgreSQL's synchronous replication does not guarantee<br>
that on standby sever the log record has been replayed when master<br>
returns a commit message. In short, there's always replication lag.<br>
<div class=""><br>
> Can You suggest us an useful solution?<br>
<br>
</div>As long as you use PostgreSQL's streaming replication, there's no<br>
solution for replication delay. Possible solution would be:<br>
<br>
1) modify your application so that it's ready for replication lag.<br>
<br>
2) use pgpool's native replication mode.<br>
<div class="HOEnZb"><div class="h5"><br>
> Thx,<br>
> Csaba<br>
><br>
><br>
> 2014-04-02 1:15 GMT+02:00 Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>>:<br>
><br>
>> Humm.. there's no error messages in the pgpool log. Maybe the<br>
>> replication lag? To make sure that if that is the cause of the<br>
>> problem, you could set the slave's backend weight to 0 and restart<br>
>> pgpool-II.<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>
>><br>
</div></div></blockquote></div><br></div>