| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | amit(dot)kapila16(at)gmail(dot)com |
| Cc: | kuroda(dot)hayato(at)fujitsu(dot)com, dilipbalaut(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Exit walsender before confirming remote flush in logical replication |
| Date: | 2023-01-16 01:31:53 |
| Message-ID: | 20230116.103153.304248162331209247.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Fri, 13 Jan 2023 16:41:08 +0530, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2023-01-16 01:52:43 | Re: Lazy allocation of pages required for verifying FPI consistency |
| Previous Message | Michael Paquier | 2023-01-16 01:28:50 | Re: Add LZ4 compression in pg_dump |