Re: Parallel execution and prepared statements

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Albe Laurenz <laurenz.albe@wien.gv.at>, Tobias Bussmann <t.bussmann@gmx.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2016-12-02T06:22:22Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Enable parallelism for prepared statements and extended query protocol.
- 57a6a72b6bc9 9.6.0 cited

Attachments

prepared_stmt_parallel_query_v3.patch (application/octet-stream) patch v3

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