On Thu, Sep 15, 2016 at 06:21:30PM -0400, Robert Haas wrote:
> On Thu, Sep 15, 2016 at 5:22 PM, Tom Lane wrote:
> > Robert Haas writes:
> >> Of course, it's also possible that the ParallelWorkerNumber code is
> >> entirely correct and something overwrote the null bytes that were
> >> supposed to
On Thu, Sep 15, 2016 at 5:22 PM, Tom Lane wrote:
> Robert Haas writes:
>> Of course, it's also possible that the ParallelWorkerNumber code is
>> entirely correct and something overwrote the null bytes that were
>> supposed to be found at that location. It would be very useful to see
>> (a) the v
Robert Haas writes:
> Of course, it's also possible that the ParallelWorkerNumber code is
> entirely correct and something overwrote the null bytes that were
> supposed to be found at that location. It would be very useful to see
> (a) the value of ParallelWorkerNumber and (b) the contents of
> v
On Sat, Aug 27, 2016 at 3:43 AM, Amit Kapila wrote:
> On Fri, Aug 26, 2016 at 6:20 PM, Tom Lane wrote:
>> Latest from lorikeet:
>> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2016-08-26%2008%3A37%3A27
>>
>> TRAP: FailedAssertion("!(vmq->mq_sender == ((void *)0))", File:
>>
On Fri, Aug 26, 2016 at 6:20 PM, Tom Lane wrote:
> Latest from lorikeet:
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2016-08-26%2008%3A37%3A27
>
> TRAP: FailedAssertion("!(vmq->mq_sender == ((void *)0))", File:
> "/home/andrew/bf64/root/REL9_6_STABLE/pgsql.build/../pgsql/
