Opened 9 months ago

Closed 9 months ago

#5500 closed defect (fixed)

ERROR: cannot drop function st_mapalgebrafct(raster,regprocedure) because other objects depend on it

Reported by: strk Owned by: pramsey
Priority: medium Milestone: PostGIS 3.4.1
Component: postgis Version: 3.4.x
Keywords: Cc:

Description

Triggered by make check-locked-upgrade RUNTESTFLAGS=-v in master branch

Change History (5)

comment:1 by strk, 9 months ago

There are 7 variants of the ST_MapAlgebraFct function, and 11 of them are in upgrade_cleanup.sql documented as having had signature or parameter names changed. Additionally there was a signature completely removed.

Pain points ++

comment:2 by strk, 9 months ago

The postgis core before-upgrade script is somewhat smarter as it uses a _drop_function_if_needed taking also parameter names, so it won't drop functions if they are not really deprecated.

It would be a good step forward to re-use that code in the raster part. Of course doing so would require finding out the name of parameters over time.

comment:3 by strk, 9 months ago

None of the current 7 ST_MapAlgebraFct changed since PostGIS 2.0.0 which was the first version having raster support integrated.

I'll remove the drops and not care about upgrading from WKTRaster times

comment:4 by Sandro Santilli <strk@…>, 9 months ago

In 83c9005/git:

Fix upgrade with objects using ST_MapAlgebraFCT

Also adds availability info to the function signatures.

References #5500 in master branch (3.5.0dev)

comment:5 by Sandro Santilli <strk@…>, 9 months ago

Resolution: → fixed
Status: new → closed

In c2a5f1c9/git:

Fix upgrade with objects using ST_MapAlgebraFCT

Also adds availability info to the function signatures.

Closes #5500 in 3.4 branch (3.4.1dev)

Note: See TracTickets for help on using tickets.