Re: Odd 9.4, 9.3 buildfarm failure on s390x
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Mark Wong <mark@2ndQuadrant.com>,
Andrew Gierth <andrew@tao11.riddles.org.uk>,
Andrew Dunstan <andrew.dunstan@2ndQuadrant.com>,
pgsql-hackers@postgresql.org
Date: 2018-10-05T20:06:15Z
Lists: pgsql-hackers
I wrote: > I'm inclined to just go ahead and apply/backpatch this. It's certainly > possible that more bugs remain to be found, but I have no good ideas > about how to search for them, and in any case that wouldn't invalidate > the patch as it stands. And done. If anyone can think of additional ways to test or search for more instances of the same bug, please do. In the meantime, I've configured buildfarm member longfin to define STRESS_SORT_INT_MIN, so it should help prevent introduction of new instances. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Allow btree comparison functions to return INT_MIN.
- 6e63e0697516 9.3.25 landed
- 60cc2414beac 9.6.11 landed
- 26cc27541d92 9.4.20 landed
- 0dc6bf633a28 9.5.15 landed
- c87cb5f7a679 12.0 landed
- 67e7d4da72dc 11.0 landed
- 142cfd3cd82e 10.6 landed