Date: Thu, 15 Dec 2022 10:52:00 +0900 (JST)
Message-Id: <20221215.105200.268327207020006785.horikyota.ntt@gmail.com>
To: amit.kapila16@gmail.com
Cc: kuroda.hayato@fujitsu.com, osumi.takamichi@fujitsu.com,
 vignesh21@gmail.com, euler@eulerto.com, m.melihmutlu@gmail.com,
 andres@anarazel.de, marcos@f10.com.br, pgsql-hackers@postgresql.org,
 smithpb2250@gmail.com
Subject: Re: Time delayed LR (WAS Re: logical replication restrictions)
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
In-Reply-To: 
 <CAA4eK1K5rb4r7FJjbnq=n7nFT=fTEg4YQs1d65aryJztTrFNuA@mail.gmail.com>
References: <20221214.103502.2162519943436870668.horikyota.ntt@gmail.com>
	<TYAPR01MB5866360932F60714625192F9F5E09@TYAPR01MB5866.jpnprd01.prod.outlook.com>
	<CAA4eK1K5rb4r7FJjbnq=n7nFT=fTEg4YQs1d65aryJztTrFNuA@mail.gmail.com>
User-Agent: Mew version 6.8 on Emacs 26.1
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20221215.105200.268327207020006785.horikyota.ntt%40gmail.com>
Precedence: bulk

At Wed, 14 Dec 2022 16:30:28 +0530, Amit Kapila <amit.kapila16@gmail.com> wrote in 
> On Wed, Dec 14, 2022 at 4:16 PM Hayato Kuroda (Fujitsu)
> <kuroda.hayato@fujitsu.com> wrote:
> > One idea to avoid that is to send the min_apply_delay subscriber option to publisher
> > and compare them, but it may be not sufficient. Because XXX_timout GUC parameters
> > could be modified later.
> >
> 
> How about restarting the apply worker if min_apply_delay changes? Will
> that be sufficient?

Mmm. If publisher knows that value, isn't it albe to delay *sending*
data in the first place? This will resolve many known issues including
walsender's un-terminatability, possible buffer-full and status packet
exchanging.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center