Message-ID: <fcbc1385-8dc5-ef31-49b1-437b3da1262c@gmail.com>
Date: Thu, 10 Nov 2022 08:00:22 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Subject: Re: WAL Async Replication Question
To: pgsql-admin@lists.postgresql.org
References: 
 <CAKgGyB-HSW8oynzPAThBB8MY9fsraL2vsQNGTZEXfsW+WkDf5g@mail.gmail.com>
Content-Language: en-US
From: Ron <ronljohnsonjr@gmail.com>
In-Reply-To: 
 <CAKgGyB-HSW8oynzPAThBB8MY9fsraL2vsQNGTZEXfsW+WkDf5g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/fcbc1385-8dc5-ef31-49b1-437b3da1262c%40gmail.com>
Precedence: bulk

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.