From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
Subject: | Re: pg_upgrade test failure |
Date: | 2022-11-17 03:15:43 |
Message-ID: | 20221117031543.GB11463@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Nov 08, 2022 at 01:16:09AM +1300, Thomas Munro wrote:
> So [1] on its own didn't fix this. My next guess is that the attached
> might help.
I took the liberty of adding a CF entry for this
https://commitfest.postgresql.org/41/4011/
And afterwards figured I could be a little bit wasteful and run the
tests using meson test --repeat, rather than let cfbot do it over the
course of a month.
https://cirrus-ci.com/task/5115893722644480
So I didn't find evidence that it doesn't resolve the issue (but this
also doesn't prove that it will works).
--
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2022-11-17 06:22:19 | pgsql: Update some more ObjectType switch statements to not have defaul |
Previous Message | Tom Lane | 2022-11-17 01:06:39 | pgsql: Improve ruleutils' printout of LATERAL references within subplan |
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Koterov | 2022-11-17 03:40:13 | Is the plan for IN(1,2,3) always the same as for =ANY('{1,2,3}') when using PQexec with no params? |
Previous Message | Michael Paquier | 2022-11-17 03:09:58 | Re: User functions for building SCRAM secrets |