Re: pgsql: Catalog changes preparing for builtin collation provider.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
Date: 2024-03-11 21:08:32
Message-ID: 1553991.1710191312@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Jeff Davis <pgsql(at)j-davis(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2024-03-11 21:09:19 pgsql: Fix 002_pg_upgrade.pl.
Previous Message Alvaro Herrera 2024-03-11 20:54:45 pgsql: Add tests for libpq query cancellation APIs