| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [External] WAL Replication query |
| Date: | 2022-11-01 13:51:57 |
| Message-ID: | 66DBCDC1-335A-463C-A7B6-8FC79D8548D4@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Nov 1, 2022, at 7:34 AM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> 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.
It comes down to this: there is no magic. Replication is async with delay between primary & secondary, or replication is synchronous with the delay visible to clients. Transaction commit completes, or it doesn't. And so on.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-11-01 13:56:30 | Re: [External] Re: WAL Replication query |
| Previous Message | Ron | 2022-11-01 13:49:52 | Re: [External] Re: WAL Replication query |