From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: parallel mode and parallel contexts |
Date: | 2015-02-07 03:43:21 |
Message-ID: | CA+Tgmob4_OeOnS4e_Kg5y=HmwNdnzLOYFLrFSfKDuTgcuEmcGA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 4, 2015 at 10:47 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I think we should expose variable ParallelWorkerNumber (or if you don't
> want to expose it then atleast GetParallel* function call is required to get
> the value of same), as that is needed for external applications wherever
> they want to allocate something for each worker, some examples w.r.t
> parallel seq scan patch are each worker should have separate tuple
> queue and probably for implementation of Explain statement also we
> might need it.
Oh, right. You asked for that before, and I made the variable itself
non-static, but didn't add the prototype to the header file. Oops.
Here's v4, with that fixed and a few more tweaks.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
parallel-mode-v4.patch | application/x-patch | 122.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-02-07 03:57:43 | Re: Parallel Seq Scan |
Previous Message | Peter Geoghegan | 2015-02-07 00:11:35 | Re: New CF app deployment |