Re: multi-install PostgresNode fails with older postgres versions
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-04-12T13:52:24Z
Lists: pgsql-hackers
On 4/12/21 8:59 AM, Jehan-Guillaume de Rorthais wrote: > Hi, > > On Wed, 7 Apr 2021 20:07:41 +0200 > Jehan-Guillaume de Rorthais <jgdr@dalibo.com> wrote: > [...] >>>> Let me know if it worth that I work on an official patch. >>> Let's give it a try ... >> OK > So, as promised, here is my take to port my previous work on PostgreSQL > source tree. > > Make check pass with no errors. The new class probably deserve some own TAP > tests. > > Note that I added a PostgresVersion class for easier and cleaner version > comparisons. This could be an interesting take away no matter what. > > I still have some more ideas to cleanup, revamp and extend the base class, but > I prefer to go incremental to keep things review-ability. > Thanks for this. We have been working somewhat on parallel lines. With your permission I'm going to take some of what you've done and incorporate it in the patch I'm working on. A PostgresVersion class is a good idea - I was already contemplating something of the kind. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Teach PostgresVersion all the ways to mark non-release code
- aa271209f6d9 14.0 landed
-
Make PostgresNode version aware
- 4c4eaf3d1920 14.0 landed
-
Avoid unfortunate IPC::Run path caching in PostgresNode
- 95c3a1956ec9 14.0 landed
-
Change pg_ctl to detect server-ready by watching status in postmaster.pid.
- f13ea95f9e47 10.0 cited