Re: Repmgr + pgbouncer - Notification of master promotion to application level ...

From: Rory Campbell-Lange <rory(at)campbell-lange(dot)net>
To: Martin Goodson <kaemaril(at)googlemail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Repmgr + pgbouncer - Notification of master promotion to application level ...
Date: 2017-06-15 06:03:46
Message-ID: 20170615060345.GA12477@campbell-lange.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 15/06/17, Martin Goodson (kaemaril(at)googlemail(dot)com) wrote:
> On 14/06/2017 19:54, Rory Campbell-Lange wrote:
> >On 14/06/17, Martin Goodson (kaemaril(at)googlemail(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ken Tanzer 2017-06-15 06:15:28 Re: Ordering of window functions with no order specified?
Previous Message David G. Johnston 2017-06-15 05:27:19 Re: Ordering of window functions with no order specified?