| From: | "Regina Obe" <lr(at)pcorp(dot)us> |
|---|---|
| To: | "'Robert Haas'" <robertmhaas(at)gmail(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:25:09 |
| Message-ID: | 000c01d9512a$88650b60$992f2220$@pcorp.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The thing that confuses me here is why the PostGIS folks are ending up with
> so many files.
> We certainly don't have that problem with the extension that
> are being maintained in contrib, and I guess there is some difference in
> versioning practice that is making it an issue for them but not for us. I wish I
> understood what was going on there.
The contrib files are minor versioned. PostGIS is micro versioned.
So we have for example postgis--3.3.0--3.3.1.sql
Also we have 5 extensions we ship all micro versions, so multiply that issue by 5
postgis
postgis_raster
postgis_topology
postgis_tiger_geocoder
postgis_sfcgal
The other wrinkle we have that I don't think postgresql's contrib have is that we support
Each version across multiple PostgreSQL versions.
So for example our 3.3 series supports PostgreSQL 12-15 (with plans to also support 16).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-03-07 19:37:34 | Re: buildfarm + meson |
| Previous Message | Tom Lane | 2023-03-07 19:13:07 | Re: [PATCH] Support % wildcard in extension upgrade filenames |