[postgis-devel] Aggregate STYPE

Paul Ramsey pramsey at cleverelephant.ca
Tue Mar 6 11:47:51 PST 2018


Actually, I think it's even more awful, all the transfns that have
func(pgis_abs) signatures will still be around, since the upgrade will
have not replaced them, but rather supplemented them with
func(internal) variants. So all the old transfns will need to be
explicitly dropped. Do we have any example of how the chicken/egg
problem of dropping a type is supposed to work?
P

On Tue, Mar 6, 2018 at 11:15 AM, Sandro Santilli <strk at kbt.io> wrote:
> On Mon, Mar 05, 2018 at 10:21:14AM -0800, Paul Ramsey wrote:
>> OK, I think I've done all the due-diligence in
>> https://trac.osgeo.org/postgis/ticket/4035
>
> I think the order of the DROPs you added won't work:
>
>   -- Old accum aggregate support type, removed in 2.5.0
>   DROP FUNCTION IF EXISTS pgis_abs_in(cstring);
>   DROP FUNCTION IF EXISTS pgis_abs_out(pgis_abs);
>   DROP TYPE IF EXISTS pgis_abs;
>
> I'd think the first two DROP FUNCTION would raise an exception
> about type pgis_abs requiring them (so can't drop). Did you try
> the upgrade ?
>
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel


More information about the postgis-devel mailing list