Re: PGBOUNCER FAILOVER AND HIGH AVAILABILITY

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Peter Wainaina <petwah17(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: PGBOUNCER FAILOVER AND HIGH AVAILABILITY
Date: 2020-05-18 06:22:32
Message-ID: 9558122d82fc8fa0215c3d8861d59774f654c0f4.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Fri, 2020-05-15 at 23:56 -0400, Peter Wainaina wrote:
> Hello hope you well ,want to implement the below:
> a) Pg-bouncer to detect a promoted standby database automatically
> b) High availability by having more than pg-bouncer

That is not pgBounder's job.

For high availability, run a pg_bouncer on each standby.

Use libpg's HA features to make the client connect to the right one:

"host=host1,host2 port=port1,port2 target_session_attrs=read-write"

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Raj kumar 2020-05-18 11:49:06 GSSAPI encryption support
Previous Message Laurenz Albe 2020-05-18 06:19:57 Re: Ip address change of Postgres Sql DB