Re: pg_upgrade test failure - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: pg_upgrade test failure
Date
Msg-id 20221117031543.GB11463@telsasoft.com
Whole thread Raw
In response to Re: pg_upgrade test failure  (Thomas Munro <thomas.munro@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: User functions for building SCRAM secrets
Next
From: Dmitry Koterov
Date:
Subject: Is the plan for IN(1,2,3) always the same as for =ANY('{1,2,3}') when using PQexec with no params?