On Thu, Jul 31, 2025 at 2:34 PM Dominique Devienne <ddevie...@gmail.com> wrote: > On Thu, Jun 5, 2025 at 4:57 AM Tom Lane <t...@sss.pgh.pa.us> wrote: > > Dominique Devienne <ddevie...@gmail.com> writes: > > > Unfortunately, digging into this is not something I can do right away. > > > v18 is still a few months out, I do hope I can investigate before that. > > > > It'd be good if you could prioritize that a bit more. If there is > > a bug rather than an intentional change here, we'd much rather > > find it and fix it before 18.0 comes out. > > Of course Tom. And as a quick update, we've installed beta2 now, but > still get the same v18-specific failure, compared to v17 and v16 (see > below). I'll be looking at this soon. And will report back. --DD
To close out this thread, I'm happy to report that all is well with v18 official. Came a bit as a surprise, given our poor experience with betas and the RC, but magically all tests pass on the official v18. So a GOOD surprise! It's not impossible this is due to recent (unrelated) changes on our end... Good thing I never investigated these v18beta/rc failures, I guess. --DD
