Streaming Replication - SLAVE )Read - Write to Read Only Scenarios - Mailing list pgsql-admin

From
Subject Streaming Replication - SLAVE )Read - Write to Read Only Scenarios
Date
Msg-id 2A91BEF8171A5349931391E0C721CC537D7796C4@CPEMS-KPN501.KPNCNL.LOCAL
Whole thread Raw
List pgsql-admin

Hi Experts,

 

 

I converted a postgres 12.1 SLAVE to read-write in case of abort/crash of MASTER(It was setup with Streaming Replication) using pg_ctl promote

 

But with pg_ctl promote there is  impact on the Master always.

 

When I bring up the MASTER and ran "select pg_is_in_recovery()" on SLAVE, it returned false.

 

postgres=# select pg_is_in_recovery();

pg_is_in_recovery

-------------------

f

 

Is there a better way to handle this and what are the options to rollback and go back to Original state?

 

pgsql-admin by date:

Previous
From: Douglas Reed
Date:
Subject: Replication Question
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade from 9.5 to 12 fails due to plpythonu2