From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
---|---|
To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Repmgr + pgbouncer - Notification of master promotion to application level ... |
Date: | 2017-06-15 06:26:03 |
Message-ID: | 20170615062603.GA13159@campbell-lange.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 15/06/17, Andreas Kretschmer (andreas(at)a-kretschmer(dot)de) wrote:
>
> Am 15.06.2017 um 01:18 schrieb Martin Goodson:
> >
> >...Do people setup pgbouncer nodes on the database servers
> >themselves, on application servers, in the middle tier between the
> >application and database, and so forth, or some combination of the
> >three?
>
> Usually we recommend to install pgbouncer on the app-servers.
>
> If you have full control of the application you can try to integrate the
> logic into the application (provide a list of servers, the new pg10-version
> of libpg is working similar in this way:
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=274bb2b3857cc987cfa21d14775cae9b0dababa5
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=721f7bd3cbccaf8c07cad2707826b83f84694832
> )
Hi Andreas
The list of servers idea is a cool enhancement. However would pgbouncer
(or another client) be able to detect which of those servers were in slave
mode?
Otherwise, if there is a temporary glitch in communications with the
master, a client (such as pgbouncer) could move to try inserts on a
slave.
Rory
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2017-06-15 06:50:45 | Re: Repmgr + pgbouncer - Notification of master promotion to application level ... |
Previous Message | Ken Tanzer | 2017-06-15 06:15:28 | Re: Ordering of window functions with no order specified? |