Postgres Pro
Downloads
Home   >   mailing lists

Re: INSERT INTO SELECT, Why Parallelism is not selected? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: INSERT INTO SELECT, Why Parallelism is not selected?
Date
Msg-id CA+TgmoYtyk5Me+Yr3PLAzKm93OYhS_iGcwOAsakD6hVFU1mYAg@mail.gmail.com
Whole thread Raw
In response to Re: INSERT INTO SELECT, Why Parallelism is not selected?  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: INSERT INTO SELECT, Why Parallelism is not selected?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Fri, Jul 24, 2020 at 7:59 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Fri, Jul 17, 2020 at 11:24 AM Amit Kapila <amit.kapila16@gmail.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

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Next
From: Tom Lane
Date:
Subject: Re: INSERT INTO SELECT, Why Parallelism is not selected?