Re: Explain [Analyze] produces parallel scan for select Into table statements.

From: Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Explain [Analyze] produces parallel scan for select Into table statements.
Date: 2016-03-11 10:04:48
Message-ID: CAD__Ouizmk7fXRcm7tB7qYYG-qHNXFuHM2m9rtB4V7CjqLLTLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 10, 2016 at 9:39 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>I guess there must not be an occurrence of this pattern in the
>regression tests, or previous force_parallel_mode testing would have
>found this problem. Perhaps this patch should add one?

I have added the test to select_into.sql. Added Explain select into
statement.
Explain Analyze produces planning time and execution time even with TIMING
OFF
so not adding the same to regress tests.

--
Thanks and Regards
Mithun C Y
EnterpriseDB: http://www.enterprisedb.com

Attachment Content-Type Size
regress_test.patch text/x-patch 1.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Grishchenko 2016-03-11 10:09:03 Re: Endless loop calling PL/Python set returning functions
Previous Message Shulgin, Oleksandr 2016-03-11 09:49:15 Re: Patch to implement pg_current_logfile() function