Opened 10 years ago
Closed 10 years ago
#3118 closed defect (fixed)
Can't upgrade 2.2.0dev to 2.2.0devnext
Reported by: | strk | Owned by: | dustymugs |
---|---|---|---|
Priority: | critical | Milestone: | PostGIS 2.2.0 |
Component: | raster | Version: | master |
Keywords: | Cc: |
Description
strk=# alter extension postgis update to '2.2.0devnext'; ERROR: cannot drop function _raster_constraint_nodata_values(raster) because other objects depend on it DETAIL: constraint enforce_nodata_values_r on table areas depends on function _raster_constraint_nodata_values(raster) HINT: Use DROP ... CASCADE to drop the dependent objects too.
Change History (11)
comment:1 by , 10 years ago
Priority: | medium → high |
---|
comment:2 by , 10 years ago
Priority: | high → medium |
---|
comment:4 by , 10 years ago
speaking of which.. we should make our upgrade tests smarter (right now we upgrade with no data tables, we should instead create some data tables first, then upgrade and then remove those tables)
comment:5 by , 10 years ago
This patch for run_test.pl makes it reproduce the issue on "make check" (or whenever it is called with switches —upgrade and —raster):
comment:7 by , 10 years ago
Priority: | medium → critical |
---|
comment:9 by , 10 years ago
I'll push the patch as soon as the bug is fixed, don't want to block the work of others closing up the release.
Note:
See TracTickets
for help on using tickets.
rtpostgis_upgrade_cleanup.sql.in contains: