<div dir="ltr">Hi,<div>for point 1) you can use keepalived and two pgpool machines</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 12:00 PM, Gintautas Sulskus <span dir="ltr"><<a href="mailto:gingaz@gmail.com" target="_blank">gingaz@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear All,<div><br></div><div>I have a few questions regarding practices with pgpool:</div><div>1. Typically pgpool is a single point of failure. What is the common practice to solve this?</div>
<div>2. Some of our data (e.g. 10% tables) must be consistent across the cluster for every transaction. The rest may differ. Is it possible to have a fine-grained replication, where some DMLs would be replicated synchronously and the rest would use asynchronous replication?<div>
<br></div><div>Thanks!</div><div><br></div>Best Regards,<br>Gintautas </div></div>
<br>_______________________________________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
<br></blockquote></div><br></div>