Horton

Re: multi-install PostgresNode fails with older postgres versions

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Mark Dilger <mark.dilger@enterprisedb.com>, Jehan-Guillaume de Rorthais <jgdr@dalibo.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-04-23T04:41:26Z
Lists: pgsql-hackers 
On Thu, Apr 22, 2021 at 08:43:10PM -0400, Andrew Dunstan wrote:
> Interesting point. Maybe we need to do something like devel = -4, alpha
> = -3, beta = -2, rc = -1. Or maybe that's overkill.

And after that it would come to how many betas, alphas or RCs you
have, but you can never be sure of how many of each you may finish
with.  I think that you have the right answer with just marking all
of them with -1 for the minor number, keeping the code a maximum
simple.
--
Michael

Commits

  1. Teach PostgresVersion all the ways to mark non-release code

  2. Make PostgresNode version aware

  3. Avoid unfortunate IPC::Run path caching in PostgresNode

  4. Change pg_ctl to detect server-ready by watching status in postmaster.pid.