| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | euler(at)eulerto(dot)com |
| Cc: | osumi(dot)takamichi(at)fujitsu(dot)com, m(dot)melihmutlu(at)gmail(dot)com, andres(at)anarazel(dot)de, amit(dot)kapila16(at)gmail(dot)com, marcos(at)f10(dot)com(dot)br, pgsql-hackers(at)postgresql(dot)org, smithpb2250(at)gmail(dot)com |
| Subject: | Re: logical replication restrictions |
| Date: | 2022-11-09 06:41:23 |
| Message-ID: | 20221109.154123.2154657548250481252.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Wed, 10 Aug 2022 17:33:00 -0300, "Euler Taveira" <euler(at)eulerto(dot)com> wrote in
> On Wed, Aug 10, 2022, at 9:39 AM, osumi(dot)takamichi(at)fujitsu(dot)com wrote:
> > Minor review comments for v6.
> Thanks for your review. I'm attaching v7.
Using interval is not standard as this kind of parameters but it seems
convenient. On the other hand, it's not great that the unit month
introduces some subtle ambiguity. This patch translates a month to 30
days but I'm not sure it's the right thing to do. Perhaps we shouldn't
allow the units upper than days.
apply_delay() chokes the message-receiving path so that a not-so-long
delay can cause a replication timeout to fire. I think we should
process walsender pings even while delaying. Needing to make
replication timeout longer than apply delay is not great, I think.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-11-09 08:12:43 | Re: New docs chapter on Transaction Management and related changes |
| Previous Message | Michael Paquier | 2022-11-09 05:28:33 | Re: User functions for building SCRAM secrets |