agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: Remove test cases for field overflows in intarray and ltree. 6+ messages / 1 participants [nested] [flat]
* pgsql: Remove test cases for field overflows in intarray and ltree. @ 2026-05-11 16:12 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2026-05-11 16:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove test cases for field overflows in intarray and ltree. These checks are failing in the buildfarm, reporting stack overflows rather than the expected errors, though seemingly only on ppc64 and s390x platforms. Perhaps there is something off about our tests for stack depth on those architectures? But there's no time to debug that right now, and surely these tests aren't too essential. Revert for now and plan to revisit after the release dust settles. Backpatch-through: 14 Security: CVE-2026-6473 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/906ea101d0d58a0b78bbe67be5fe54976c0a21e6 Modified Files -------------- contrib/intarray/expected/_int.out | 3 --- contrib/intarray/sql/_int.sql | 2 -- contrib/ltree/expected/ltree.out | 13 ------------- contrib/ltree/sql/ltree.sql | 11 ----------- 4 files changed, 29 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Remove test cases for field overflows in intarray and ltree. @ 2026-05-11 16:12 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2026-05-11 16:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove test cases for field overflows in intarray and ltree. These checks are failing in the buildfarm, reporting stack overflows rather than the expected errors, though seemingly only on ppc64 and s390x platforms. Perhaps there is something off about our tests for stack depth on those architectures? But there's no time to debug that right now, and surely these tests aren't too essential. Revert for now and plan to revisit after the release dust settles. Backpatch-through: 14 Security: CVE-2026-6473 Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/05e73b5c3578cb9857dfd4904d8dc2a96e0b04eb Modified Files -------------- contrib/intarray/expected/_int.out | 3 --- contrib/intarray/sql/_int.sql | 2 -- contrib/ltree/expected/ltree.out | 13 ------------- contrib/ltree/sql/ltree.sql | 11 ----------- 4 files changed, 29 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Remove test cases for field overflows in intarray and ltree. @ 2026-05-11 16:12 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2026-05-11 16:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove test cases for field overflows in intarray and ltree. These checks are failing in the buildfarm, reporting stack overflows rather than the expected errors, though seemingly only on ppc64 and s390x platforms. Perhaps there is something off about our tests for stack depth on those architectures? But there's no time to debug that right now, and surely these tests aren't too essential. Revert for now and plan to revisit after the release dust settles. Backpatch-through: 14 Security: CVE-2026-6473 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/2b429d887b23284e7c2c4767cf381daf03932075 Modified Files -------------- contrib/intarray/expected/_int.out | 3 --- contrib/intarray/sql/_int.sql | 2 -- contrib/ltree/expected/ltree.out | 13 ------------- contrib/ltree/sql/ltree.sql | 11 ----------- 4 files changed, 29 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Remove test cases for field overflows in intarray and ltree. @ 2026-05-11 16:12 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2026-05-11 16:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove test cases for field overflows in intarray and ltree. These checks are failing in the buildfarm, reporting stack overflows rather than the expected errors, though seemingly only on ppc64 and s390x platforms. Perhaps there is something off about our tests for stack depth on those architectures? But there's no time to debug that right now, and surely these tests aren't too essential. Revert for now and plan to revisit after the release dust settles. Backpatch-through: 14 Security: CVE-2026-6473 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/6f0bff33d780aac82d147a309afe505d79974086 Modified Files -------------- contrib/intarray/expected/_int.out | 3 --- contrib/intarray/sql/_int.sql | 2 -- contrib/ltree/expected/ltree.out | 13 ------------- contrib/ltree/sql/ltree.sql | 11 ----------- 4 files changed, 29 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Remove test cases for field overflows in intarray and ltree. @ 2026-05-11 16:12 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2026-05-11 16:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove test cases for field overflows in intarray and ltree. These checks are failing in the buildfarm, reporting stack overflows rather than the expected errors, though seemingly only on ppc64 and s390x platforms. Perhaps there is something off about our tests for stack depth on those architectures? But there's no time to debug that right now, and surely these tests aren't too essential. Revert for now and plan to revisit after the release dust settles. Backpatch-through: 14 Security: CVE-2026-6473 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/fc1fd3d970d400fcc37979bcb012d4657dbab1f5 Modified Files -------------- contrib/intarray/expected/_int.out | 3 --- contrib/intarray/sql/_int.sql | 2 -- contrib/ltree/expected/ltree.out | 13 ------------- contrib/ltree/sql/ltree.sql | 11 ----------- 4 files changed, 29 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Remove test cases for field overflows in intarray and ltree. @ 2026-05-11 16:12 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2026-05-11 16:12 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove test cases for field overflows in intarray and ltree. These checks are failing in the buildfarm, reporting stack overflows rather than the expected errors, though seemingly only on ppc64 and s390x platforms. Perhaps there is something off about our tests for stack depth on those architectures? But there's no time to debug that right now, and surely these tests aren't too essential. Revert for now and plan to revisit after the release dust settles. Backpatch-through: 14 Security: CVE-2026-6473 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/479823a71042423ad832e0d17ba11ff4c2bfa588 Modified Files -------------- contrib/intarray/expected/_int.out | 3 --- contrib/intarray/sql/_int.sql | 2 -- contrib/ltree/expected/ltree.out | 13 ------------- contrib/ltree/sql/ltree.sql | 11 ----------- 4 files changed, 29 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2026-05-11 16:12 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-05-11 16:12 pgsql: Remove test cases for field overflows in intarray and ltree. Tom Lane <tgl@sss.pgh.pa.us> 2026-05-11 16:12 pgsql: Remove test cases for field overflows in intarray and ltree. Tom Lane <tgl@sss.pgh.pa.us> 2026-05-11 16:12 pgsql: Remove test cases for field overflows in intarray and ltree. Tom Lane <tgl@sss.pgh.pa.us> 2026-05-11 16:12 pgsql: Remove test cases for field overflows in intarray and ltree. Tom Lane <tgl@sss.pgh.pa.us> 2026-05-11 16:12 pgsql: Remove test cases for field overflows in intarray and ltree. Tom Lane <tgl@sss.pgh.pa.us> 2026-05-11 16:12 pgsql: Remove test cases for field overflows in intarray and ltree. Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox