Oh, sorry I made a typo, it should be "is always async". I was
referring to this statement in docs about cascading replication:
"Cascading replication is currently asynchronous". It sounds to me
like the whole replication setup is async (M -> U ->D), but it's only
the (U -> D) part that is always async. But probably it's a topic for
another thread.
My original problem was with the first sentence "It should be noted
that log shipping is asynchronous". I think your original suggestion
"It should be noted that by default, log shipping is asynchronous"
sounds good as it highlights from the beginning that there is some
variety.
On Tue, Sep 2, 2025 at 9:34 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> On Mon, 2025-09-01 at 13:51 +0200, Artem Gavrilov wrote:
> > As I understand in configuration `Master
> > -> Upstream -> Downstream` replication between Master And Upstream
> > still can be synchronous, while between Upstream and Downstream is't
> > always async. Am I wrong here?
>
> I don't quite understand. Sure, you can have synchronous replication
> between the master and upstream. It is the "isn't always async" part
> that confuses me. Do you mean that WAL can reach downstream before
> the master commits? That is certainly the case.
>
> Yours,
> Laurenz Albe
--
Artem Gavrilov
Senior Software Engineer, Percona
artem.gavrilov@percona.com
