Re: parallel mode and parallel contexts - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parallel mode and parallel contexts
Date
Msg-id CA+Tgmob4_OeOnS4e_Kg5y=HmwNdnzLOYFLrFSfKDuTgcuEmcGA@mail.gmail.com
Whole thread Raw
In response to Re: parallel mode and parallel contexts  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: parallel mode and parallel contexts  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Wed, Feb 4, 2015 at 10:47 PM, Amit Kapila <amit.kapila16@gmail.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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: New CF app deployment
Next
From: Robert Haas
Date:
Subject: Re: Parallel Seq Scan