Re: PG version is not seen in pg_upgrade test log
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Potapov Alexander <a.potapov@postgrespro.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-12-03T00:47:56Z
Lists: pgsql-hackers
On Tue, Dec 02, 2025 at 11:22:36AM +0100, Daniel Gustafsson wrote: > This seems like a correct change, reading the history around this code makes it > seem like it just happened to end up in the wrong place in one of many > refactorings. Indeed. It looks like this should be backpatched down to v15 for two reasons: Cluster.pm exists since v15 and pg_upgrade has been converted to TAP since v15. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Show version of nodes in output of TAP tests
- 7e54eacc5c06 15.16 landed
- b38feca1ce00 16.12 landed
- 9d4f6d17f579 17.8 landed
- 28c5be4aecda 18.2 landed
- 83f2f8413e8d 19 (unreleased) landed