| From: | Rui DeSousa <rui(at)crazybean(dot)net> |
|---|---|
| To: | Pierre Ochsenbein <pierreochsenbein(at)gmail(dot)com> |
| Cc: | Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2018-11-05 16:59:58 |
| Message-ID: | EA4685AD-1D43-4CDD-B7F7-DEF15AFA13D1@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Nov 5, 2018, at 11:25 AM, Pierre Ochsenbein <pierreochsenbein(at)gmail(dot)com> wrote:
>
> but on your stdby you have configure a script to become the primary automatically?
Yes, as soon at the CARP address (i.e. the VIP) is migrated to the standby the database is promoted automatically. All the existing TCP connections are reset/dropped and the clients reconnect to the new server within seconds.
You have to researched the best solution for your given OS platform. There are solutions that are platform agnostic too. I don’t have a canned one to recommend though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikhil Shetty | 2018-11-06 04:41:42 | Re: hot standby cascading replication |
| Previous Message | Rui DeSousa | 2018-11-05 16:48:03 | Re: PostgreSQL 10.5 : Strange pg_wal fill-up, solved with the shutdown checkpoint |