| From: | "Regina Obe" <lr(at)pcorp(dot)us> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Robert Haas'" <robertmhaas(at)gmail(dot)com> |
| Cc: | "'Sandro Santilli'" <strk(at)kbt(dot)io>, "'Regina Obe'" <r(at)pcorp(dot)us>, <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [PATCH] Support % wildcard in extension upgrade filenames |
| Date: | 2023-03-07 19:39:07 |
| Message-ID: | 000d01d9512c$7c3c2e70$74b48b50$@pcorp.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-03-07 19:47:19 | Re: Add shared buffer hits to pg_stat_io |
| Previous Message | Andres Freund | 2023-03-07 19:37:34 | Re: buildfarm + meson |