| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT INTO SELECT, Why Parallelism is not selected? |
| Date: | 2020-07-24 13:53:50 |
| Message-ID: | CA+TgmoYtyk5Me+Yr3PLAzKm93OYhS_iGcwOAsakD6hVFU1mYAg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 24, 2020 at 7:59 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Fri, Jul 17, 2020 at 11:24 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> > Do you have something else in mind?
>
> I am planning to commit the comments change patch attached in the
> above email [1] next week sometime (probably Monday or Tuesday) unless
> you have something more to add?
Well, I think the comments could be more clear - for the insert case
specifically - about which cases you think are and are not safe.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-24 14:06:53 | Re: INSERT INTO SELECT, Why Parallelism is not selected? |
| Previous Message | Tom Lane | 2020-07-24 13:48:36 | Re: Row estimates for empty tables |