On 15/06/17, Martin Goodson (kaema...@googlemail.com) wrote: > On 14/06/2017 19:54, Rory Campbell-Lange wrote: > >On 14/06/17, Martin Goodson (kaema...@googlemail.com) wrote: > >>The new master's repmgr promote script will execute commands to pause > >>pgbouncer, reconfigure pgbouncer to point to the new database address, and > >>then resume. > > > >You could just move the service ip address at the new postgresql master > >to which the pgbouncer instances on each app server could reconnect. > > > >I assume, with reference to https://github.com/2ndQuadrant/repmgr, that > >you could use repmgrd to trigger a script to do just that at > >"switchover", possibly something you would need to monitor the > >"repl_events" table to achieve.
> I'm just wondering how people may have implemented this. Do people setup > pgbouncer nodes on the database servers themselves, on application servers, We have pgbouncer on the application servers and shift the postgres master ip address to the promoted master. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
