Opened 10 years ago

Closed 10 years ago

#2944 closed defect (fixed)

ERROR: aggregate st_astwkbagg(geometry, integer, bigint, boolean) does not exist

Reported by: strk Owned by: strk
Priority: medium Milestone: PostGIS 2.2.0
Component: postgis Version: master
Keywords: Cc:

Description

I cannot upgrade between 2.2.0dev and 2.2.0devnext, due to the change in TKWB aggregate signature:

=# alter extension postgis update to '2.2.0devnext';
ERROR:  aggregate st_astwkbagg(geometry, integer, bigint, boolean) does not exist

Source PostGIS version is 2.2.0dev r13012

Change History (6)

comment:1 by strk, 10 years ago

It might be actually related to the comments, as mentioned on the mailing list...

comment:2 by strk, 10 years ago

Ah, got it. It's the usual in-development upgrade problem.

The script that generates the upgrade does NOT include the ST_AsTWKBAgg function because it was added in the same version we come from (2.2.0). So there's no such function when it comes to add a comment for it, which is instead added unconditionally.

I've the impression we had another ticket for this issue, and someone suggested to always re-define the "same-version" objects while in "-dev" mode. Remember about it robe ?

comment:3 by strk, 10 years ago

Owner: changed from nicklas to strk

I'm trying the "same-dev-version" trick. Seems to work.

comment:4 by strk, 10 years ago

The problem with that is you could still get an error upgrading from a dev version to another revision of the same dev version while having views relying on aggregates. Is that ok to keep ?

The alternative would be to include revision number in the availability tag...

comment:5 by strk, 10 years ago

With r13013 all aggregates added in a version are always dropped/reloaded when upgrading to the same in-development version (but not when upgrading between patch-levels)

comment:6 by strk, 10 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.