pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
Date: Mon, 11 Mar 2024 17:08:32 -0400
Message-ID: <1553991.1710191312@sss.pgh.pa.us> (raw)
In-Reply-To: <0ef325fa06e7a1605c4e119c4ecb637c67e5fb4e.camel@j-davis.com>
References: <E1rj5WA-002z5V-WA@gemulon.postgresql.org>
	<8899c7c62b86370076110920686fd24863b69a01.camel@j-davis.com>
	<1222780.1710047108@sss.pgh.pa.us>
	<0ef325fa06e7a1605c4e119c4ecb637c67e5fb4e.camel@j-davis.com>

Jeff Davis <pgsql@j-davis.com> writes:
> My commit adds a line using the s/// operator.

Oh, independently of the empty-pattern problem: what you added is

+# Numeric major version of old cluster, ignoring "devel" suffix.
+# Needed for testing upgrades from development version to itself.
+my $old_major_version = int($oldnode->pg_version =~ s/devel//rg);

Surely this will break the moment we enter beta.  Rather than
trying to fix that directly, what we should be doing is realizing
that you've reinvented -- badly -- the facilities provided by
the PostgreSQL::Version package.  The code you changed,

	if ($oldnode->pg_version >= 15 && $ENV{with_icu} eq 'yes')

was perfectly correct as it stood, because pg_version is a
PostgreSQL::Version object.  Why did you feel a need to
editorialize on that?

			regards, tom lane





view thread (12+ messages)  latest in thread

Message-ID: <1553991.1710191312@sss.pgh.pa.us>
Permalink:  ../1553991.1710191312@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1553991.1710191312@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pgsql@j-davis.com, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
  In-Reply-To: <1553991.1710191312@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox