[postgis-devel] Upgrading

[Mark Cave-Ayland]

Paul Ramsey wrote:

> I'm still hammering away at a soft upgrade script. I now have one that 
> runs through to completion, upgrading most of the functions. This is 
> still using the old model of parsing the new postgis.sql file. When I'm 
> done, I have the following functions "left over", in that there was no 
> definition in the new postgis.sql file that overwrote them.
> 
>          proname         |      probin
> -------------------------+-------------------
>  histogram2d_in          | $libdir/liblwgeom
>  st_histogram2d_in       | $libdir/liblwgeom
>  histogram2d_out         | $libdir/liblwgeom
>  st_histogram2d_out      | $libdir/liblwgeom
>  dump                    | $libdir/liblwgeom
>  create_histogram2d      | $libdir/liblwgeom
>  st_create_histogram2d   | $libdir/liblwgeom
>  build_histogram2d       | $libdir/liblwgeom
>  st_build_histogram2d    | $libdir/liblwgeom
>  explode_histogram2d     | $libdir/liblwgeom
>  st_explode_histogram2d  | $libdir/liblwgeom
>  estimate_histogram2d    | $libdir/liblwgeom
>  st_estimate_histogram2d | $libdir/liblwgeom
>  postgis_jts_version     | $libdir/liblwgeom
>  text                    | $libdir/liblwgeom
>  st_text                 | $libdir/liblwgeom
>  jtsnoop                 | $libdir/liblwgeom
>  _st_asgml               | $libdir/liblwgeom

This all looks sane except for the _st_asgml() function - although it's 
difficult to tell which one it is as there are multiple versions with 
different arguments. Can you work out which one this is exactly?


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063