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

From Amit Kapila
Subject Re: INSERT INTO SELECT, Why Parallelism is not selected?
Date
Msg-id CAA4eK1JPCd=GowHHkpri=T4KG6DrJnDj-u4nh434YCyR5cu3vw@mail.gmail.com
Whole thread Raw
In response to Re: INSERT INTO SELECT, Why Parallelism is not selected?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: INSERT INTO SELECT, Why Parallelism is not selected?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jul 24, 2020 at 7:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Robert Haas <robertmhaas@gmail.com> writes:
> > Well, I think the comments could be more clear - for the insert case
> > specifically - about which cases you think are and are not safe.
>

Okay, I'll update the patch accordingly.

> Yeah, the proposed comment changes don't actually add much.  Also
> please try to avoid inserting non-ASCII   into the source code;
> at least in my mail reader, that attachment has some.
>

I don't see any non-ASCII characters in the patch.  I have applied and
checked (via vi editor) the patch as well but don't see any non-ASCII
characters.  How can I verify that?

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Row estimates for empty tables
Next
From: Michael Paquier
Date:
Subject: Re: handle a ECPG_bytea typo