From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: [External] Re: WAL Replication query |
Date: | 2022-11-01 07:43:46 |
Message-ID: | 8f9e6c92-4daa-a543-6825-05a3503f4296@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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?
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2022-11-01 13:34:42 | Re: [External] Re: WAL Replication query |
Previous Message | Sacheen Birhade | 2022-11-01 07:00:39 | finding best possible new master in case of failover? |