public inbox for [email protected]
help / color / mirror / Atom feedFrom: Kyotaro Horiguchi <[email protected]>
To: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: Exit walsender before confirming remote flush in logical replication
Date: Mon, 16 Jan 2023 10:31:53 +0900 (JST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA4eK1LmCfLcu2hV_NCL9m0iQaE9=g7f8ePj79da373haFdZ-A@mail.gmail.com>
References: <CAA4eK1+pD654+XnrPugYueh7Oh22EBGTr6dA_fS0+gPiHayG9A@mail.gmail.com>
<TYAPR01MB5866E7B0583504FBDE6B60FAF5F29@TYAPR01MB5866.jpnprd01.prod.outlook.com>
<CAA4eK1LmCfLcu2hV_NCL9m0iQaE9=g7f8ePj79da373haFdZ-A@mail.gmail.com>
At Fri, 13 Jan 2023 16:41:08 +0530, Amit Kapila <[email protected]> wrote in
> Okay, but what happens in the case of physical replication when
> synchronous_commit = remote_apply? In that case, won't it ensure that
> apply has also happened? If so, then shouldn't the time delay feature
> also cause a similar problem for physical replication as well?
As written in another mail, WalSndDone doesn't honor
synchronous_commit. In other words, AFAIS walsender finishes not
waiting remote_apply. The unapplied recods will be applied at the
next startup.
I didn't confirmed that behavior for myself, though..
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
view thread (3+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Exit walsender before confirming remote flush in logical replication
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox