From: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Fix comment in btree_gist--1.8--1.9.sql |
Date: | 2025-07-09 17:37:16 |
Message-ID: | 75a89911-bbef-4f7d-913b-d34632bf66ce@illuminatedcomputing.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/9/25 08:51, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> On Tue, Jul 08, 2025 at 04:49:30PM -0700, Paul Jungwirth wrote:
>>> A related question: In the v18 release we are adding two upgrade files:
>>> btree_gist--1.7--1.8.sql and btree_gist--1.8-1.9.sql. Why not collapse them
>>> into one? Technically we briefly had btree_gist--1.7--1.8.sql in 17devel,
>>> but it was reverted before release. Would you like a patch combining these
>>> files? Is it too late for that?
>
>> It would be too late once the branch is officially released, and we
>> are still in a position where it is possible to combine both. Let's
>> do so for REL_18_STABLE, having two upgrade paths for a single major
>> version is just extra work for no benefit.
>
> +1 for merging those two while we still can.
Patch attached, based on REL_18_STABLE.
I considered putting the sortsupport functions first, since they have a lower support function
number, but I thought defining them in the same order as we've been doing was a tiny bit safer.
Maybe that is superstitious.
Yours,
--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Collapse-last-two-releases-of-btree_gist-into-1.8.patch | text/x-patch | 15.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2025-07-09 17:46:29 | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Previous Message | Tom Lane | 2025-07-09 17:36:26 | Re: [PoC] Federated Authn/z with OAUTHBEARER |