Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader

From: Andreas Seltenreich <seltenreich(at)gmx(dot)de>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader
Date: 2016-04-30 08:21:23
Message-ID: 87mvobeccc.fsf@credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Kapila writes:

> On Fri, Apr 29, 2016 at 7:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> but it might be worth copying over the full query from the parent
>> side.
>
> That would amount to couple of extra cycles considering we need to do it
> for each worker, but OTOH it might be a useful debugging information in the
> cases as reported in this thread.

Maybe only do it in assertion-enabled builds when performance is an
issue?

regards,
andreas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2016-04-30 08:54:09 Re: Rename max_parallel_degree?
Previous Message Andreas Seltenreich 2016-04-30 08:17:23 Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader