Re: multi-install PostgresNode fails with older postgres versions

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multi-install PostgresNode fails with older postgres versions
Date: 2021-04-24 05:54:54
Message-ID: YIOyOGkecKnyl3eA@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 23, 2021 at 08:10:01AM -0400, Andrew Dunstan wrote:
> Yeah, I think it's ok for comparison purposes just to lump them all
> together. Here's a patch that does that and some consequent cleanup.
> Note we now cache the string rather than trying to reconstruct it.

No objections from here to build the version string beforehand.

> + (devel|(?:alpha|beta|rc)\d+)? # dev marker - see version_stamp.pl
> + !x);

I have been playing with patch and version_stamp.pl, and that does the
job. Nice.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2021-04-24 06:08:04 Re: pg_identify_object_as_address() doesn't support pg_event_trigger oids
Previous Message Justin Pryzby 2021-04-24 02:57:35 Re: [PATCH] force_parallel_mode and GUC categories