RE: [PATCH] Support % wildcard in extension upgrade filenames

Regina Obe <lr@pcorp.us>

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>

Date: 2023-03-07T19:39:07Z

Lists: pgsql-hackers

> 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.
> 
> 			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