Streaming Replication - SLAVE )Read - Write to Read Only Scenarios

From: <soumik(dot)bhattacharjee(at)kpn(dot)com>
To: <pgsql-admin(at)lists(dot)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org>
Subject: Streaming Replication - SLAVE )Read - Write to Read Only Scenarios
Date: 2020-01-21 13:33:24
Message-ID: 2A91BEF8171A5349931391E0C721CC537D7796C4@CPEMS-KPN501.KPNCNL.LOCAL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2020-01-21 15:29:53 Re: pg_upgrade from 9.5 to 12 fails due to plpythonu2
Previous Message Douglas Reed 2020-01-21 10:41:04 Replication Question