From: | Mark Wong <mark(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-03 17:08:59 |
Message-ID: | 20190503170859.GB20049@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 02, 2019 at 11:45:34AM -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > Hm, I just noticed:
> > 'HEAD' => [
> > 'force_parallel_mode = regress'
> > ]
>
> Oooh, I didn't see that.
>
> > on all those animals. So it's not necessarily the case that HEAD and
> > backbranch runs are behaving all that identical. Note that isn't a
> > recent config change, so it's not an explanation as to why they started
> > to fail only recently.
>
> No, but it does point at another area of the code in which a relevant
> change could've occurred.
>
> While we're looking at this --- Mark, if you could install gdb
> on your buildfarm hosts, that would be really handy. I think that's
> the only extra thing the buildfarm script needs to extract stack
> traces from core dumps. We'd likely already know where the problem
> is if we had a stack trace ...
Ok, I think I have gdb installed now...
Regards,
Mark
--
Mark Wong
2ndQuadrant - PostgreSQL Solutions for the Enterprise
https://www.2ndQuadrant.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-03 18:19:20 | Re: Why is infinite_recurse test suddenly failing? |
Previous Message | Robert Haas | 2019-05-03 17:01:38 | Re: Per-tablespace autovacuum settings |