Re: Why is infinite_recurse test suddenly failing?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Wong <mark(at)2ndQuadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why is infinite_recurse test suddenly failing?
Date: 2019-05-14 14:40:17
Message-ID: 15442.1557844817@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Wong <mark(at)2ndQuadrant(dot)com> writes:
> The following I've enabled force_parallel_mode for HEAD, 11, 10, and
> 9.6:

Thanks Mark!

In theory, the stack trace we now have from shoveler proves that parallel
mode has nothing to do with this, because the crash happens during
planning (specifically, inlining SQL functions). I wonder though if
it's possible that previous force_parallel_mode queries have had some
undesirable effect on the process's stack allocation. Just grasping
at straws, because it's sure not clear what's going wrong.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-05-14 14:52:07 Re: Why is infinite_recurse test suddenly failing?
Previous Message Mark Wong 2019-05-14 14:31:40 Re: Why is infinite_recurse test suddenly failing?