<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Lou,<div> I'm afraid that I<i> </i>want to have the same design as you, but it simply doesnt exist right now in PGPool. Right now the behavior is EITHER:</div><div><br></div><div>a) failover is allowed, and the instance any postgres server goes down the appropriate failover scripts are called</div><div>b) failover is DISALLOWED, and the instant any postgres server goes down, your entire pgpool server basically freezes all connections until the servers come back up.</div><div><br></div><div> There's no middle ground... I'm actually talking to one of my engineers in house and we're thinking about patching PGPool so that we can have a behavior where:</div><div><br></div><div>If DISALLOW_TO_FAILOVER is set and ..</div><div> a) one of the slaves fails: that slave is taken out of rotation until its back up</div><div> b) the master fails: all connections hang until the master is back, OR a new master is detected. pgpool goes into a loop looking for new masters.</div><div><br></div><div>—Matt</div><div><br><div><div>On Apr 19, 2012, at 6:27 PM, Lou Kamenov wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hey there,<br><br>I have been looking at a setup which includes couple of pgpool servers<br>and about four PostgreSQL nodes in a 1 master, 3 slaves streaming<br>replication configuration.<br><br>From what I've seen PgPool performs the fallback to backend1 the<br>moment the master disappears, but in case of two pgpool nodes which<br>point to the same set of servers, what would the behavior be?<br><br>In effect, the first pgpool that detects the failing master will do<br>the switch and trigger the slave into master mode, what would the<br>other pgpool do, attempt to trigger backend1 into master mode as well?<br>will it detect that the master was already triggered, etc.<br><br>I will be trying this in practice but would be great to hear other<br>peoples experience.<br><br>Thanks in advance!<br>Lou<br>_______________________________________________<br>pgpool-general mailing list<br><a href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a><br>http://www.pgpool.net/mailman/listinfo/pgpool-general<br></div></blockquote></div><br></div></body></html>