| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Logical decoding of TRUNCATE |
| Date: | 2020-12-21 06:59:37 |
| Message-ID: | CAA4eK1KXpXV2DqEc32WKmpPQJvKNLm9RD0jCqV7BGYLGK=Oo7Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Sun, Dec 20, 2020 at 9:43 AM Noah Misch <noah(at)leadboat(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2020-12-21 09:39:04 | Re: [PATCH] Logical decoding of TRUNCATE |
| Previous Message | Peter Geoghegan | 2020-12-20 23:54:31 | Re: [PATCH] Logical decoding of TRUNCATE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2020-12-21 07:02:29 | Dependency isn't created between extension and schema |
| Previous Message | Bharath Rupireddy | 2020-12-21 06:31:38 | Re: Fail Fast In CTAS/CMV If Relation Already Exists To Avoid Unnecessary Rewrite, Planning Costs |