From: "Regina Obe" <lr@pcorp.us>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>,
	"'Robert Haas'" <robertmhaas@gmail.com>
Cc: "'Sandro Santilli'" <strk@kbt.io>,
	"'Regina Obe'" <r@pcorp.us>,
	<pgsql-hackers@lists.postgresql.org>
References: <YgakFklJyM5pNdt+@c19> <20221117095734.igldlk6kngr6ogim@c19> <166914379479.1121.7549798686571352890.pgcf@coridan.postgresql.org> <55512.1673304709@sss.pgh.pa.us> <20230110205259.htcuhg3t7shd367d@c19> <387183.1673394631@sss.pgh.pa.us> <CA+TgmobDy0sasmzOFkCcKXC3XeQZzRNwbaQRJ752tF1i11BRKQ@mail.gmail.com> <4025573.1678216387@sss.pgh.pa.us>
In-Reply-To: <4025573.1678216387@sss.pgh.pa.us>
Subject: RE: [PATCH] Support % wildcard in extension upgrade filenames
Date: Tue, 7 Mar 2023 14:39:07 -0500
Message-ID: <000d01d9512c$7c3c2e70$74b48b50$@pcorp.us>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQGYmaaUCwtlrmE55CHyCSUXu9VHkgKopfE4AVtxnv8DArAuyQGehsdEA0I4l/UBweK/cwF/FZ4frvffErA=
Content-Language: en-us
Archived-At: <https://www.postgresql.org/message-id/000d01d9512c%247c3c2e70%2474b48b50%24%40pcorp.us>
Precedence: bulk

> I'm not unsympathetic to the idea of trying to support multiple =
upgrade paths
> in one script.  I just don't like this particular design for that, =
because it
> requires the extension author to make promises that nobody is actually =
going
> to deliver on.
>=20
> 			regards, tom lane

How about the idea I mentioned, of we revise the patch to read versioned =
upgrades from the control file
rather than relying on said file to exist.

https://www.postgresql.org/message-id/000201d92572%247dcd8260%2479688720%=
24%40pcorp.us

Even better, we have an additional control file, something like

postgis--paths.control

That has separate lines to itemize those paths.  It would be nice if we =
could allow wild-cards in that, but I could live without that if we can =
stop shipping 300 empty files.

Thanks,
Regina