Re: Parallel execution and prepared statements - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Parallel execution and prepared statements
Date
Msg-id CAA4eK1L52xWojr0NQayM7iB6+FFimYiF7wgvxj7g_+B3tPyA8g@mail.gmail.com
Whole thread Raw
In response to Re: Parallel execution and prepared statements  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Parallel execution and prepared statements  (Tobias Bussmann <t.bussmann@gmx.net>)
List pgsql-hackers
On Thu, Dec 1, 2016 at 9:40 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Dec 1, 2016 at 7:57 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>
>> I have tried to restrict all the non-readonly operation modes or modes
>> where parallelism might not make sense like DestTupleStore.  If we
>> want to just prohibit the cases where it can fail now, then I think
>> prohibiting only DestIntoRel should be sufficient because that is a
>> case where the user is allowed to do DDL for an already prepared read
>> only statement like Create Table AS .. EXECUTE.
>
> OK, then my vote is to do it that way for now.
>

Done that way in attached patch.

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

Attachment

pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: pgbench more operators & functions
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench more operators & functions