Message-ID: <66ec0be7.170a0220.48a0.7d07@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Thu, 19 Sep 2024 13:32:54 +0200
From: Michael Banck <mbanck@gmx.net>
To: "Narendran .j" <jnarendran3@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Failover and Failback
References: 
 <CA+-Cqf6b2FY3nJuOL==XsUyVqSev47gXR57u8t5z2LfNZSLAaA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CA+-Cqf6b2FY3nJuOL==XsUyVqSev47gXR57u8t5z2LfNZSLAaA@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/66ec0be7.170a0220.48a0.7d07%40mx.google.com>
Precedence: bulk

Hi,

On Thu, Sep 19, 2024 at 04:46:28PM +0530, Narendran .j wrote:
> I have facing a problem in failback. I just promoted my secondary as master
> by using pg_ctl promote.it was successful.so now how can I bring my old
> master as primary I tried with pg_rewind it's not working. 

You need to bring your old primary as standby first, then switchover
back to it - otherwise, you would have two primaries, no?

In general, pg_rewind is the only reasonable way to recover a failed
over primary other than by rebuilding it from scratch as a standby.

So if pg_rewind did not work, we would need more information, like what
command did you issue exactly and what was the output/error message?


Michael