Opened 2 years ago
Closed 15 months ago
#5052 closed enhancement (fixed)
Add support for specifying target version in postgis_extensions_upgrade()
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.4.0 |
| Component: | build | Version: | master |
| Keywords: | Cc: |
Description
At the moment postgis_extensions_upgrade() always attempts an upgrade to the default version of all postgis extensions. In some cases the user might want to upgrade to a specific version which is NOT the default one.
This ticket is to implement such functionality.
Change History (4)
comment:1 by , 22 months ago
| Component: | postgis → build/upgrade/install |
|---|---|
| Owner: | changed from to |
comment:2 by , 22 months ago
| Milestone: | PostGIS 3.3.0 → PostGIS Fund Me |
|---|
comment:3 by , 20 months ago
| Milestone: | PostGIS Fund Me → PostGIS 3.4.0 |
|---|
Note:
See TracTickets
for help on using tickets.
Might be worthwhile as part of this using a procedure instead.
So we introduce a CREATE PROCEDURE postgis_extensions_upgrade(target_version).
That way we can keep the existing, but have it do CALL. So no breaking changes.
Since the CREATE PROCEDURE has a different signature from existing, it can coexist.