Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Logical decoding of TRUNCATE - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] Logical decoding of TRUNCATE
Date
Msg-id CAA4eK1KXpXV2DqEc32WKmpPQJvKNLm9RD0jCqV7BGYLGK=Oo7Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Logical decoding of TRUNCATE  (Noah Misch <noah@leadboat.com>)
Responses Re: [PATCH] Logical decoding of TRUNCATE
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Fail Fast In CTAS/CMV If Relation Already Exists To Avoid Unnecessary Rewrite, Planning Costs
Next
From: Masahiko Sawada
Date:
Subject: Dependency isn't created between extension and schema