Re: PG version is not seen in pg_upgrade test log
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Potapov Alexander <a.potapov@postgrespro.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-12-02T10:22:36Z
Lists: pgsql-hackers
> On 30 Nov 2025, at 10:11, Potapov Alexander <a.potapov@postgrespro.com> wrote: > I ran pg_upgrade tests (make check -C src/bin/pg_upgrade) and found that test log does not contain PG version: > - $node->dump_info; > - > $node->_set_pg_version; > + $node->dump_info; > + 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. -- Daniel Gustafsson
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