| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Rushabh Lathia <rushabh(dot)lathia(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 17:33:34 |
| Message-ID: | CA+TgmoYO9G02RzLCjOWPnCwRdka-DABezsGMrc4r7qDZGne8pg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 16, 2016 at 1:05 AM, Rushabh Lathia
<rushabh(dot)lathia(at)gmail(dot)com> wrote:
> 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.
Looks good, committed. I am not sure it was a very good idea for
af33039317ddc4a0e38a02e2255c2bf453115fd2 by Tom Lane to change the
current memory context for the entire execution of gather_readnext();
this might not be the only or the last bug that results from that
decision. However, I don't really want to get an argument about that
right now, and this at least fixes the problem we know about. Thanks
for the report and patch.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joy Arulraj | 2016-08-16 17:53:43 | Re: [GENERAL] C++ port of Postgres |
| Previous Message | Robert Haas | 2016-08-16 17:13:06 | Re: [GENERAL] C++ port of Postgres |