On Tue, Aug 16, 2016 at 1:05 AM, Rushabh Lathia
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
On Mon, Aug 15, 2016 at 6:02 PM, Robert Haas wrote:
> On Sat, Aug 13, 2016 at 4:36 AM, Amit Kapila
> wrote:
> > AFAICS, your patch seems to be the right fix for this issue, unless we
> > need the instrumentation information during execution (other
On Sat, Aug 13, 2016 at 4:36 AM, Amit Kapila 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
On Sat, Aug 13, 2016 at 11:10 AM, Rushabh Lathia
wrote:
> Hi All,
>
> Recently while running tpc-h queries on postgresql master branch, I am
> noticed
> random server crash. Most of the time server crash coming while turn tpch
> query
> number 3 - (but its very random).
Hi All,
Recently while running tpc-h queries on postgresql master branch, I am
noticed
random server crash. Most of the time server crash coming while turn tpch
query
number 3 - (but its very random).
Call Stack of server crash:
(gdb) bt
#0 0x102aa9ac in ExplainNode