Re: Re-add recently-removed tests for ltree and intarray

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Michael Paquier <michael@paquier.xyz>, Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-05-15T02:47:04Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Re-add regression tests for ltree and intarray
- 092b570a72dd 14 (unreleased) landed
- 4503c9771683 15 (unreleased) landed
- f71f72e89abf 16 (unreleased) landed
- a6c430cabedc 17 (unreleased) landed
- f45f418275b1 18 (unreleased) landed
- 27bdae84137f 19 (unreleased) landed
Remove test cases for field overflows in intarray and ltree.
- 906ea101d0d5 19 (unreleased) cited

On Fri, May 15, 2026 at 9:09 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> (b) the failure only appeared on buildfarm members running on ppc64
> or s390x.  I determined by examining assembly code that ppc64 uses
> about 3X as much stack per call level in this function as x86_64;
> probably s390x is similar.  That was enough to overrun our default
> max_stack_depth on these architectures, even though the same case
> passed on the machines we'd tested on.

FWIW, I tried to reproduce with the former new tests un-reverted, and
didn't see stack overflow on the following, so unless I fat-fingered
that I wonder if there's something more specific on the previously
failing members:

ppc64le / gcc 8.5 / Linux kernel 4.18
S390X / gcc 13.3 / Linux kernel 6.8

-- 
John Naylor
Amazon Web Services