Why is infinite_recurse test suddenly failing?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: mark(at)2ndQuadrant(dot)com
Subject: Why is infinite_recurse test suddenly failing?
Date: 2019-05-02 15:02:03
Message-ID: 26111.1556809323@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

In the past week, four different buildfarm members have shown
non-reproducing segfaults in the "select infinite_recurse()"
test case, rather than the expected detection of stack overrun
before we get to the point of a segfault.


They're all on HEAD, and they all look like

2019-05-01 23:11:00.145 UTC [13933:65] LOG: server process (PID 17161) was terminated by signal 11: Segmentation fault
2019-05-01 23:11:00.145 UTC [13933:66] DETAIL: Failed process was running: select infinite_recurse();

I scraped the buildfarm database and verified that there are no similar
failures for at least three months back; nor, offhand, can I remember ever
having seen this test fail in many years. So it seems we broke something
recently. No idea what though.

(Another possibility, seeing that these are all members of Mark's PPC64
flotilla, is that there's some common misconfiguration --- but it's hard
to credit that such a problem would only affect HEAD not the back


regards, tom lane


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-05-02 15:08:43 Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6
Previous Message Ibrar Ahmed 2019-05-02 14:54:38 Re: pgbench - add option to show actual builtin script code