pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
WAL Async Replication Question
2+ messages / 2 participants
[nested] [flat]

* WAL Async Replication Question
@ 2022-11-10 08:27  KK CHN <kkchn.in@gmail.com>
  0 siblings, 1 reply; 2+ messages in thread

From: KK CHN @ 2022-11-10 08:27 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org

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.

Any hints / directions most welcome .. How will geeks do this in this
situation?

Yours,
Krishane

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: WAL Async Replication Question
@ 2022-11-10 14:00  Ron <ronljohnsonjr@gmail.com>
  parent: KK CHN <kkchn.in@gmail.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Ron @ 2022-11-10 14:00 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org

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.





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2022-11-10 14:00 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-11-10 08:27 WAL Async Replication Question KK CHN <kkchn.in@gmail.com>
2022-11-10 14:00 ` Ron <ronljohnsonjr@gmail.com>

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