| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: assessing parallel-safety |
| Date: | 2015-03-25 10:37:04 |
| Message-ID: | CAA4eK1Kpi0v1TUWM93vxDfuOwm7t-hhT6ck-UXVntr_-tGoWrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 20, 2015 at 11:37 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>
> That might be a different crash than the first one you showed. But it
> looks like the problem here is that the parallel sequential scan patch
> is calling CreateParallelContext even though this is just an EXPLAIN
> and we're not actually running the query. It shouldn't do that.
> (This might be an argument for postponing CreateParallelContext()
> until run time, as I've suggested before.)
>
Okay, I have postponed the CreateParallelContext() until runtime in
the latest patch posted on Parallel Seq Scan thread.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-03-25 10:37:29 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
| Previous Message | Amit Kapila | 2015-03-25 10:35:04 | Re: assessing parallel-safety |