| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT INTO SELECT, Why Parallelism is not selected? |
| Date: | 2020-07-14 18:55:23 |
| Message-ID: | CA+TgmoagAKn8dpjOa4VFk7hZ8H__UpX4uGGWe=umG8or2UgMTQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 11, 2020 at 8:37 AM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> I have just notice that the parallelism is off even for the select
> part of the query mentioned in the $subject. I see the only reason it
> is not getting parallel because we block the parallelism if the query
> type is not SELECT. I don't see any reason for not selecting the
> parallelism for this query.
There's a relevant comment near the top of heap_prepare_insert().
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-07-14 18:58:28 | Re: warnings for invalid function casts |
| Previous Message | Tom Lane | 2020-07-14 18:36:37 | Re: Binary support for pgoutput plugin |