Opened 15 months ago
Last modified 2 months ago
#5487 new defect
Confusing error when upgrading from partially upgraded database
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.4.4 |
Component: | upgrade | Version: | master |
Keywords: | Cc: |
Description
This is a spin off of #5486
When upgrading your PostGIS database while having a view holding back a deprecated function you end up having a partially upgraded database, which is reported with a WARNING during the upgrade and by postgis_full_version()
When upgrading again you don't get a clear message about problems BUT you may get an error about being it impossible to rename a deprecated function (because the deprecated function name already exists).
This ticket may serve to improve this situation.
Change History (3)
comment:1 by , 13 months ago
Component: | build → upgrade |
---|
comment:2 by , 13 months ago
Milestone: | PostGIS Fund Me → PostGIS 3.5.0 |
---|
comment:3 by , 2 months ago
Milestone: | PostGIS 3.5.0 → PostGIS 3.4.4 |
---|
Note:
See TracTickets
for help on using tickets.
I switched this from Fund me to 3.5.0, I'll pay for it.