From: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [parallel query] random server crash while running tpc-h query on power2 |
Date: | 2016-08-16 05:05:23 |
Message-ID: | CAGPqQf2_Vrn_GzXc_k88xrG=h1c9QwoZ_f4pJ2YUu9bJbJb9RQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 15, 2016 at 6:02 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Aug 13, 2016 at 4:36 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
> > AFAICS, your patch seems to be the right fix for this issue, unless we
> > need the instrumentation information during execution (other than for
> > explain) for some purpose.
>
> Hmm, I disagree. It should be the job of
> ExecParallelRetrieveInstrumentation to allocate its data in the
> correct context, not the responsibility of nodeGather.c to work around
> the fact that it doesn't. The worker instrumentation should be
> allocated in the same context as the regular instrumentation
> information, which I assume is probably the per-query context.
>
I agree, this make sense.
Here is the patch to allocate worker instrumentation into same context
as the regular instrumentation which is per-query context.
PFA patch.
--
Rushabh Lathia
www.EnterpriseDB.com
Attachment | Content-Type | Size |
---|---|---|
worker_instrument_allocation_fix.patch | text/x-patch | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Venkata B Nagothi | 2016-08-16 05:08:25 | Re: patch proposal |
Previous Message | amul sul | 2016-08-16 05:04:06 | Re: Bug in to_timestamp(). |