Re: [External] Re: WAL Replication query - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: [External] Re: WAL Replication query
Date
Msg-id f78c361061449be8402922cd5ed7f5782f65aab1.camel@cybertec.at
Whole thread Raw
In response to Re: [External] Re: WAL Replication query  (Ron <ronljohnsonjr@gmail.com>)
Responses Re: [External] Re: WAL Replication query
Re: [External] WAL Replication query
List pgsql-admin
On Tue, 2022-11-01 at 02:43 -0500, Ron wrote:
> On 11/1/22 01:53, Laurenz Albe wrote:
> > On Tue, 2022-11-01 at 06:44 +0000, Sacheen Birhade wrote:
> > > If replication is in asynchronous then there will be data loss, right Laurenz?
> >
> > Why?  The data will perhaps show up on the standby a little later, but why is
> > that data loss?  Remember that the question was about replication, and there
> > was no mention of failover.
> 
>  No, the question was about a crash during replication: OP (not Sacheen, unless that person
> is using two email addresses) explicitly asked "When the primary crashes  due an unforeseen
> reason (what happens)?"
>  
>  If the two database systems are really busy, and especially if the network connection
> isn't fast enough, async replication means there might be some transactions committed
> on Primary which were queued for transmission, but hadn't yet made it to the Secondary, right?

Right.  And how does that constitute data loss?  If you start the primary again, the transaction
will be replicated just fine.  Now if you call it *data delay*, I would agree.

Yours,
Laurenz Albe



pgsql-admin by date:

Previous
From: Ron
Date:
Subject: Re: [External] Re: WAL Replication query
Next
From: Laurenz Albe
Date:
Subject: Re: finding best possible new master in case of failover?