Re: [PATCH] Logical decoding of TRUNCATE

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: [PATCH] Logical decoding of TRUNCATE
Дата
Msg-id CAA4eK1KXpXV2DqEc32WKmpPQJvKNLm9RD0jCqV7BGYLGK=Oo7Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Logical decoding of TRUNCATE  (Noah Misch <noah@leadboat.com>)
Ответы Re: [PATCH] Logical decoding of TRUNCATE  (Noah Misch <noah@leadboat.com>)
Список pgsql-hackers
Дерево обсуждения 
On Sun, Dec 20, 2020 at 9:43 AM Noah Misch <noah@leadboat.com> wrote:
>
> Since commit 039eb6e added logical replication support for TRUNCATE, logical
> apply of the TRUNCATE fails if it chooses a parallel index build:
>

I think the TRUNCATE operation should not use parallelism either via
apply worker or without it because there is nothing to scan in heap.
Additionally, we can have an Assert or elog in InitializeParallelDSM
to ensure that it is never invoked by parallel worker.

-- 
With Regards,
Amit Kapila.

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

Предыдущее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Fail Fast In CTAS/CMV If Relation Already Exists To Avoid Unnecessary Rewrite, Planning Costs
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Dependency isn't created between extension and schema