<div dir="ltr">So, no longer did I write this than i found a command called pcp_attach_node that seems to get it all working. Typical!<div><br></div><div>However, given the complexity of some of the other solutions I am wondering whether this isn't actually doing what I think it is ... specifically, with respect to pcp_recovery_node.</div><div><br></div><div>steven</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 30, 2015 at 9:16 PM, Steven Livingstone <span dir="ltr"><<a href="mailto:steven@livz.org" target="_blank">steven@livz.org</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">Hello - this is my first real step into the world of Postgres and Pgpool.<div><br></div><div>I have managed to get a simple two node Postgres master/slave cluster working, using Postgres Streaming Replication. Works well.</div><div><br></div><div>I have then added Pgpool (one instance for now, tho looking at HA), added the master/slave above as backends and that works fine. Then I turn on load balancing, set master_slave_mode=true and sure enough, i can bring down one and the other takes over.</div><div><br></div><div>However, when I bring the slave down, even when reattached it stays at status=3 which i know is node down.</div><div><br></div><div>Now, I have researched and threads around this go back a number of years and much of what I tried didn't quite work ... i suspect it applies when I use PGpool streaming replication rather than the SR now part of Postgres.</div><div><br></div><div>Does anyone have a fairly straightforward guide/suggestion on how to use the Postgres SR in Master/Slave config, along with PGpool when I can add nodes back (or rather make them available) into the pgpool?</div><div><br></div><div>Been a fairly steep learning curve but hoping to sort it by next year ;-)</div><div><br></div><div>thanks,</div><div>steven</div></div>
</blockquote></div><br></div>