From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: WAL Async Replication Question
Date: Thu, 10 Nov 2022 08:00:22 -0600
Message-ID: <fcbc1385-8dc5-ef31-49b1-437b3da1262c@gmail.com> (raw)
In-Reply-To: <CAKgGyB-HSW8oynzPAThBB8MY9fsraL2vsQNGTZEXfsW+WkDf5g@mail.gmail.com>
References: <CAKgGyB-HSW8oynzPAThBB8MY9fsraL2vsQNGTZEXfsW+WkDf5g@mail.gmail.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: WAL Async Replication Question
In-Reply-To: <fcbc1385-8dc5-ef31-49b1-437b3da1262c@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox