From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul A Jungwirth <pj@illuminatedcomputing.com>
cc: Adrian Klaver <adrian.klaver@aklaver.com>,
        Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>,
        "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
In-reply-to: <CA+renyU=3z2J_yLaz1BFk9sHeO1Gnu=KMof5vcb-diW1_JZggQ@mail.gmail.com>
References: <4d301501-9985-4e68-b1c1-2360c251048c@cloud.gatewaynet.com> <54d352ad-3f64-4492-aaaf-1ebaeac5471c@aklaver.com> <CA+renyU=3z2J_yLaz1BFk9sHeO1Gnu=KMof5vcb-diW1_JZggQ@mail.gmail.com>
Comments: In-reply-to Paul A Jungwirth <pj@illuminatedcomputing.com>
	message dated "Wed, 20 Aug 2025 09:49:31 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1020347.1755701903.1@sss.pgh.pa.us>
Date: Wed, 20 Aug 2025 10:58:23 -0400
Message-ID: <1020348.1755701903@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1020348.1755701903%40sss.pgh.pa.us>
Precedence: bulk

Paul A Jungwirth <pj@illuminatedcomputing.com> writes:
> I don't know what pg_upgrade tries to support for moving from one beta
> release to another. Is this something we should try to fix?

It's water over the dam now, I think.  If we had such a breakage
between officially-released versions, that would be bad enough to
justify jumping through hoops.  But beta releases have always been
"use at your own risk".

			regards, tom lane