pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: [External] WAL Replication query
Date: Tue, 1 Nov 2022 07:51:57 -0600
Message-ID: <66DBCDC1-335A-463C-A7B6-8FC79D8548D4@elevated-dev.com> (raw)
In-Reply-To: <f78c361061449be8402922cd5ed7f5782f65aab1.camel@cybertec.at>
References: <CAKgGyB-SMT0RxeoifAfjkRx6RHEOgpn7sf8F_zD1DPsKydTu=w@mail.gmail.com>
	<88faef33e966796226022d6e7f3e32ad6c59fcfd.camel@cybertec.at>
	<MW4PR20MB4525ED0222DDE9FED0519D8FF3369@MW4PR20MB4525.namprd20.prod.outlook.com>
	<c1b6b89d6b89706acaeca9b4d45958f4739c4f28.camel@cybertec.at>
	<8f9e6c92-4daa-a543-6825-05a3503f4296@gmail.com>
	<f78c361061449be8402922cd5ed7f5782f65aab1.camel@cybertec.at>

> On Nov 1, 2022, at 7:34 AM, Laurenz Albe <laurenz.albe@cybertec.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.




view thread (15+ messages)  latest in thread

Message-ID: <66DBCDC1-335A-463C-A7B6-8FC79D8548D4@elevated-dev.com>
Permalink:  ../66DBCDC1-335A-463C-A7B6-8FC79D8548D4@elevated-dev.com/
Also on:    postgresql.org/message-id/66DBCDC1-335A-463C-A7B6-8FC79D8548D4@elevated-dev.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott_ribe@elevated-dev.com, laurenz.albe@cybertec.at, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: [External] WAL Replication query
  In-Reply-To: <66DBCDC1-335A-463C-A7B6-8FC79D8548D4@elevated-dev.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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