Re: Skipping logical replication transactions on subscriber side

Поиск
Список
Период
Сортировка
От Alexey Lesovsky
Тема Re: Skipping logical replication transactions on subscriber side
Дата
Msg-id CAGnetYciM4jDCYcf+v1uFLQ5Bm2Kp41MpxW_n8ey-SWiR5guoQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Skipping logical replication transactions on subscriber side  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: Skipping logical replication transactions on subscriber side
Список pgsql-hackers
Дерево обсуждения
On Mon, Jul 12, 2021 at 8:36 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> Ok, looks nice. But I am curious how this will work in the case when there are two (or more) errors in the same subscription, but different relations?
>

We can't proceed unless the first error is resolved, so there
shouldn't be multiple unresolved errors. 

Ok. I thought multiple errors are possible when many tables are initialized using parallel workers (with max_sync_workers_per_subscription > 1).

--
Regards, Alexey


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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: More time spending with "delete pending"
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Skipping logical replication transactions on subscriber side