| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Manual Failover |
| Date: | 2024-06-19 17:07:56 |
| Message-ID: | CANzqJaDi+Jb6tA+cx2Z-NMcLXVS_ZLr-7OSq3QLQmATC9_r1YA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 19, 2024 at 11:03 AM Yongye Serkfem <yserkfem(at)gmail(dot)com> wrote:
> Hello Engineers,
> I am facing an issue with the manual failover of the standby to the master
> role. I was able to promote the standby and got it out of recovery mode.
> How do I direct applications to point to the standby which has assumed the
> role of the current master,
>
A typical solution is a separate service which manages a virtual IP that
points to whichever DB server you choose.
> and what should I do after completing maintenance on the previous master
> to assume its original role as master?
>
pg_basebackup is guaranteed to get previous-master in sync with
now-active. pg_rewind might also work.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2024-06-19 17:13:56 | Re: Proper format for pg_dump file date |
| Previous Message | David G. Johnston | 2024-06-19 16:50:44 | Re: Seeking Clarification on Function Definitions in PostgreSQL Extensions |