From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: WAL Async Replication Question |
Date: | 2022-11-10 14:00:22 |
Message-ID: | fcbc1385-8dc5-ef31-49b1-437b3da1262c@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 11/10/22 02:27, KK CHN wrote:
> List,
>
> I've done WAL async replication between two Postgre servers in Pirmary
> and Standby node as a test bed on two Virtual Machines on CentOS 8.
> Postgres12.
>
> Now I want to do the same WAL replication on a Production Postgres
> server to a new standby server.
>
> Is there a way to do configurations for WAL async replication on primary
> server without affecting the customers / applications that depend on this
> primary DB server?
>
> As it is a production server, any changes we make to configuration files
> may affect the services right ? or what unseen problems can arise in this
> use case?
>
> How to minimize the downtime / without service interruptions from the
> Primary server while doing WAL replication to a Standby server.
As long as "wal_level = replica" (which is the default) you do not need to
stop and restart the Primary instance. Testing should have demonstrated
that to you.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Edwin UY | 2022-11-10 14:59:20 | How to test replication without doing a failover |
Previous Message | KK CHN | 2022-11-10 08:27:54 | WAL Async Replication Question |