On Sat, Nov 7, 2020 at 11:33 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Wed, Nov 4, 2020 at 10:58 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> >
> > In the tablesync stage, we don't allow streaming. See pgoutput_startup
> > where we disable streaming for the init phase. As far as I understand,
> > for tablesync we create the initial slot during which streaming will
> > be disabled then we will copy the table (here logical decoding won't
> > be used) and then allow the apply worker to get any other data which
> > is inserted in the meantime.
>
> I think this assumption is not completely correct, because if the
> tablesync worker is behind the apply worker then it will start the
> streaming by itself until it reaches from CATCHUP to SYNC DONE state.
> So during that time if streaming is on then the tablesync worker will
> also send the streaming on.
>
Yeah, this seems to be possible and this is the reason I mentioned
above to dig more into this case. Did you try it via some test case? I
think we can generate a test via debugger where after the tablesync
worker reaches CATCHUP state stop it via debugger, then we can perform
some large transaction on the same table which apply worker will skip
and tablesync worker will try to apply changes and should fail.
> I think for disabling the streaming in
> the tablesync worker we can do something like this.
>
Sure, but why do we want to prohibit streaming in tablesync worker
unless there is some fundamental reason for the same? If we can write
a test based on what I described above then we can probably know if
there is any real issue with allowing streaming via tablesync worker.
--
With Regards,
Amit Kapila.