From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: parallelize queries containing subplans |
Date: | 2017-01-12 03:21:46 |
Message-ID: | CA+TgmobgOhvn4UYY_38q3o8X_MiRw8Edj+2Hy+5QDrEjumU+ow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 11, 2017 at 9:58 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> The other alternative is to remember this information in SubPlan. We
> can retrieve parallel_safe information from best_path and can use it
> while generating SubPlan. The main reason for storing it in the plan
> was to avoid explicitly passing parallel_safe information while
> generating SubPlan as plan was already available at that time.
> However, it seems there are only two places in code (refer
> build_subplan) where this information needs to be propagated. Let me
> know if you prefer to remember the parallel_safe information in
> SubPlan instead of in Plan or if you have something else in mind?
I think we should try doing it in the SubPlan, at least, and see if
that comes out more elegant than what you have at the moment.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2017-01-12 03:21:50 | Re: merging some features from plpgsql2 project |
Previous Message | Robert Haas | 2017-01-12 03:20:31 | Re: Gather Merge |