| From: | Sandro Santilli <strk(at)kbt(dot)io> |
|---|---|
| To: | Regina Obe <lr(at)pcorp(dot)us> |
| Cc: | 'Yurii Rashkovskii' <yrashk(at)gmail(dot)com>, 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, '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-04-11 21:27:37 |
| Message-ID: | 20230411212737.phtzffycglbdhmpx@c19 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 11, 2023 at 04:36:04PM -0400, Regina Obe wrote:
>
> > Hey, best would be having support for wildcard wouldn't it ?
>
> I'm a woman of compromise. Sure 1 file would be ideal, but
> I'd rather live with a big file listing all version upgrades
> than 1000 files with the same information.
Personally I don't see the benefit of 1 big file vs. many 0-length
files to justify the cost (time and complexity) of a PostgreSQL change,
with the corresponding cost of making use of this new functionality
based on PostgreSQL version.
We'd still have the problem of missing upgrade paths unless we release
a new version of PostGIS even if it's ONLY for the sake of updating
that 1 big file (or adding a new file, in the current situation).
--strk;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Kimura | 2023-04-11 21:28:32 | Unexpected (wrong?) result querying boolean partitioned table with NULL partition |
| Previous Message | Daniel Gustafsson | 2023-04-11 21:12:58 | Re: Various typo fixes |