Re: [External] Re: WAL Replication query

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: [External] Re: WAL Replication query
Date: 2022-11-01 13:34:42
Message-ID: f78c361061449be8402922cd5ed7f5782f65aab1.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2022-11-01 13:37:17 Re: finding best possible new master in case of failover?
Previous Message Ron 2022-11-01 07:43:46 Re: [External] Re: WAL Replication query