Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop
Дата
Msg-id CAA4eK1JWLho8Ghhe0BJTHMt4TB9bG+LNDYpSfUYy0VkL9MLoJQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop  (Dilip Kumar <dilipbalaut@gmail.com>)
Список pgsql-bugs
On Mon, Nov 9, 2020 at 1:33 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Mon, Nov 9, 2020 at 11:50 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > On Sat, Nov 7, 2020 at 11:33 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> >
> > 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.
>
> I think there is no fundamental reason for the same,  but I thought it
> is just an initial catchup state so does it make sense to stream the
> transaction.  But if we want to stream then we need to put some
> handling in apply_handle_stream_commit so that it can avoid committing
> if this is the table-sync worker.
>

Sure, let's try that then instead of blindly avoid streaming if it is possible.

-- 
With Regards,
Amit Kapila.



В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16706: insert into on conflict(pk) do update error violates not-null constraint
Следующее
От: 德哥
Дата:
Сообщение: Re:Re: BUG #16702: inline code and function : when use dynamic name for rowtype, there is some bug!