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

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>
Cc: Robert Haas <robertmhaas(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-13 05:11:43
Message-ID: CAA4eK1Kz97OauE1LCfrMnSEGymXdK2y+30fwrifq-bqir86-OQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 12, 2016 at 7:11 PM, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>
wrote:
>
>
>
> On Sat, Mar 12, 2016 at 2:32 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
> >With force_parallel_mode=on, I could see many other failures as well. I
think it is better to have test, which tests this functionality with
>force_parallel_mode=regress
>
> as per user manual.
> Setting this value to regress has all of the same effects as setting it
to on plus some additional effect that are intended to facilitate automated
> regression testing.
>

Yes, that is the only reason I mentioned that it better to have a test
which can be checked in automated way and I understand that the way you
have written test using Explain won't work in automated way, so not sure if
it is good idea to add such a test.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Regina Obe 2016-03-13 05:32:48 Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue
Previous Message Matt Kelly 2016-03-13 03:46:11 Re: amcheck (B-Tree integrity checking tool)