Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
Worked great. Thanks! On 11-7-2012 13:39, Paragon Corporation wrote: In the postgis_upgrade_20_minor.sql file, there are a bunch of drop commands at the end. Just run those and you should be fine. Regina http://www.postgis.us ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
In the postgis_upgrade_20_minor.sql file, there are a bunch of drop commands at the end. Just run those and you should be fine. Regina http://www.postgis.us > -Original Message- > From: postgis-users-boun...@postgis.refractions.net > [mailto:postgis-users-boun...@postgis.refractions.net] On > Behalf Of Tom van Tilburg > Sent: Wednesday, July 11, 2012 3:54 AM > To: postgis-users@postgis.refractions.net > Subject: Re: [postgis-users] possible bug: function > st_asgeojson(geometry) is not unique > > Thanks Regina and Strk for the enlightment on this. > I will definately stay with the old-fashioned way then, since > I use release candidates quite often and prefer to be bitten > as least as possible. > > A final question: > Provided that I had a fresh postgis extension on my > database but contaminated it by using a restore from data > that included postgis stuff, what would be the best way to > clean up my current database? > > Best regards, > Tom > > > > On 11-7-2012 2:53, Paragon Corporation wrote: > > The only issue I see with CREATE EXTENSION at this point is that if > > you want to use the subversion releases because they don't have > > extension version points (which CREATE EXTENSION requires freeze > > points) , it's not upgradeable. I have a work around for > that issue > > which I'm experimenting with. That only affects people who want to > > live on the edge like strk. > > > > If you always go with released versions, it works just > dandy from my > > experience. So in a nut-shell its fine for production use, > just hard > > to use for interim synching with repository version. > > > > strk is just against it because he got bitten once early on > and he had > > a mixed bag of stuff anyway. > > > > As far as upgrading from say 1.5. If you did an unclean upgrade -- > > brought over junk and installed on top of a clean postgis 2.0, YOU > > NEED to run the postgis_upgrade_minor script or you'll get > ambiguous > > function calls as you've experienced. > > > > Hope that helps, > > Regina > > http://www.postgis.us > > > > > > > > > > > > > > > >> -----Original Message- > >> From: postgis-users-boun...@postgis.refractions.net > >> [mailto:postgis-users-boun...@postgis.refractions.net] On > Behalf Of > >> Tom van Tilburg > >> Sent: Tuesday, July 10, 2012 6:33 AM > >> To: postgis-users@postgis.refractions.net > >> Subject: Re: [postgis-users] possible bug: function > >> st_asgeojson(geometry) is not unique > >> > >> On 10-7-2012 12:16, Sandro Santilli wrote: > >>>> Also I see no double functions in public.functions nor are there > >>>> functions in any other place installed in the database. > >>> select * from pg_proc where proname = 'st_asgeojson'; (I > >> have 5 rows) > >> Seems I spoke too soon.. I just created a brand new empty database > >> and added postgis by extension. > >> It worked correctly. > >> > >> The previous database was also new but I imported a lot of > data that > >> came from an earlier postgis database. Seems I accidently > copied some > >> postgis functions somewhere because "select * from pg_proc where > >> proname = 'st_asgeojson';" > >> returned 11 rows (!). > >> > >> Thanks for your input! > >> > >> P.S. Do I understand correctly that CREATE EXTENSION is not a > >> preferred method for postgis? > >> ___ > >> postgis-users mailing list > >> postgis-users@postgis.refractions.net > >> http://postgis.refractions.net/mailman/listinfo/postgis-users > >> > > > > ___ > > postgis-users mailing list > > postgis-users@postgis.refractions.net > > http://postgis.refractions.net/mailman/listinfo/postgis-users > > > ___ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
Thanks Regina and Strk for the enlightment on this. I will definately stay with the old-fashioned way then, since I use release candidates quite often and prefer to be bitten as least as possible. A final question: Provided that I had a fresh postgis extension on my database but contaminated it by using a restore from data that included postgis stuff, what would be the best way to clean up my current database? Best regards, Tom On 11-7-2012 2:53, Paragon Corporation wrote: The only issue I see with CREATE EXTENSION at this point is that if you want to use the subversion releases because they don't have extension version points (which CREATE EXTENSION requires freeze points) , it's not upgradeable. I have a work around for that issue which I'm experimenting with. That only affects people who want to live on the edge like strk. If you always go with released versions, it works just dandy from my experience. So in a nut-shell its fine for production use, just hard to use for interim synching with repository version. strk is just against it because he got bitten once early on and he had a mixed bag of stuff anyway. As far as upgrading from say 1.5. If you did an unclean upgrade -- brought over junk and installed on top of a clean postgis 2.0, YOU NEED to run the postgis_upgrade_minor script or you'll get ambiguous function calls as you've experienced. Hope that helps, Regina http://www.postgis.us -Original Message- From: postgis-users-boun...@postgis.refractions.net [mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Tom van Tilburg Sent: Tuesday, July 10, 2012 6:33 AM To: postgis-users@postgis.refractions.net Subject: Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique On 10-7-2012 12:16, Sandro Santilli wrote: Also I see no double functions in public.functions nor are there functions in any other place installed in the database. select * from pg_proc where proname = 'st_asgeojson'; (I have 5 rows) Seems I spoke too soon.. I just created a brand new empty database and added postgis by extension. It worked correctly. The previous database was also new but I imported a lot of data that came from an earlier postgis database. Seems I accidently copied some postgis functions somewhere because "select * from pg_proc where proname = 'st_asgeojson';" returned 11 rows (!). Thanks for your input! P.S. Do I understand correctly that CREATE EXTENSION is not a preferred method for postgis? ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
The only issue I see with CREATE EXTENSION at this point is that if you want to use the subversion releases because they don't have extension version points (which CREATE EXTENSION requires freeze points) , it's not upgradeable. I have a work around for that issue which I'm experimenting with. That only affects people who want to live on the edge like strk. If you always go with released versions, it works just dandy from my experience. So in a nut-shell its fine for production use, just hard to use for interim synching with repository version. strk is just against it because he got bitten once early on and he had a mixed bag of stuff anyway. As far as upgrading from say 1.5. If you did an unclean upgrade -- brought over junk and installed on top of a clean postgis 2.0, YOU NEED to run the postgis_upgrade_minor script or you'll get ambiguous function calls as you've experienced. Hope that helps, Regina http://www.postgis.us > -Original Message- > From: postgis-users-boun...@postgis.refractions.net > [mailto:postgis-users-boun...@postgis.refractions.net] On > Behalf Of Tom van Tilburg > Sent: Tuesday, July 10, 2012 6:33 AM > To: postgis-users@postgis.refractions.net > Subject: Re: [postgis-users] possible bug: function > st_asgeojson(geometry) is not unique > > On 10-7-2012 12:16, Sandro Santilli wrote: > >> Also I see no double functions in public.functions nor are there > >> functions in any other place installed in the database. > > select * from pg_proc where proname = 'st_asgeojson'; (I > have 5 rows) > > > Seems I spoke too soon.. I just created a brand new empty > database and added postgis by extension. > It worked correctly. > > The previous database was also new but I imported a lot of > data that came from an earlier postgis database. Seems I > accidently copied some postgis functions somewhere because > "select * from pg_proc where proname = 'st_asgeojson';" > returned 11 rows (!). > > Thanks for your input! > > P.S. Do I understand correctly that CREATE EXTENSION is not a > preferred method for postgis? > ___ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
On Tue, Jul 10, 2012 at 12:32:57PM +0200, Tom van Tilburg wrote: > On 10-7-2012 12:16, Sandro Santilli wrote: > >>Also I see no double functions in public.functions nor are there > >>functions in any other place installed in the database. > >select * from pg_proc where proname = 'st_asgeojson'; > >(I have 5 rows) > > > Seems I spoke too soon.. I just created a brand new empty database > and added postgis by extension. > It worked correctly. > > The previous database was also new but I imported a lot of data that > came from an earlier postgis database. Seems I accidently copied > some postgis functions somewhere because "select * from pg_proc > where proname = 'st_asgeojson';" returned 11 rows (!). Great. > Thanks for your input! > > P.S. Do I understand correctly that CREATE EXTENSION is not a > preferred method for postgis? It's actually a personal thing. I don't like it because it doesn't let you easily upgrade between SVN revisions. There's no known bug about it other than that (given yours was a false alarm :) --strk; ,--o-. | __/ |Delivering high quality PostGIS 2.1 | / 2.1 |http://strk.keybit.net - http://vizzuality.com `-o--' ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
On 10-7-2012 12:16, Sandro Santilli wrote: Also I see no double functions in public.functions nor are there functions in any other place installed in the database. select * from pg_proc where proname = 'st_asgeojson'; (I have 5 rows) Seems I spoke too soon.. I just created a brand new empty database and added postgis by extension. It worked correctly. The previous database was also new but I imported a lot of data that came from an earlier postgis database. Seems I accidently copied some postgis functions somewhere because "select * from pg_proc where proname = 'st_asgeojson';" returned 11 rows (!). Thanks for your input! P.S. Do I understand correctly that CREATE EXTENSION is not a preferred method for postgis? ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
On Tue, Jul 10, 2012 at 11:57:33AM +0200, Tom van Tilburg wrote: > I upgraded my postgis libraries from 2.0.0 to 2.0.1 but did a clean > install with CREATE EXTENSION to a new database after that. Could be a bug with CREATE EXTENSION. Could you try with "the old way" to confirm ? If confirmed, this will be very worth opening a ticket for. > Also I see no double functions in public.functions nor are there > functions in any other place installed in the database. select * from pg_proc where proname = 'st_asgeojson'; (I have 5 rows) > version output is: > "POSTGIS="2.0.1 r9979" GEOS="3.3.5-CAPI-1.7.5" PROJ="Rel. 4.8.0, > 6 March 2012" GDAL="GDAL 1.9.1, released 2012/05/15" LIBXML="2.7.8" > TOPOLOGY RASTER" > > Does it work for you? Yes, but only tried on a pre-existing database, and not enabled with CREATE EXTENSION. --strk; ,--o-. | __/ |Delivering high quality PostGIS 2.1 | / 2.1 |http://strk.keybit.net - http://vizzuality.com `-o--' ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
I upgraded my postgis libraries from 2.0.0 to 2.0.1 but did a clean install with CREATE EXTENSION to a new database after that. Also I see no double functions in public.functions nor are there functions in any other place installed in the database. version output is: "POSTGIS="2.0.1 r9979" GEOS="3.3.5-CAPI-1.7.5" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.9.1, released 2012/05/15" LIBXML="2.7.8" TOPOLOGY RASTER" Does it work for you? On 10-7-2012 11:38, Sandro Santilli wrote: On Tue, Jul 10, 2012 at 11:35:20AM +0200, Tom van Tilburg wrote: ERROR: function st_asgeojson(geometry) is not unique Sounds like an unclean upgrade (coexistance of old and new st_asgeojson signatures, one with default args, one without). Does loading the minor upgrade script fixes it ? What does SELECT postgis_full_version() tells you ? --strk; ,--o-. | __/ |Delivering high quality PostGIS 2.1 | / 2.1 |http://strk.keybit.net - http://vizzuality.com `-o--' ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
Re: [postgis-users] possible bug: function st_asgeojson(geometry) is not unique
On Tue, Jul 10, 2012 at 11:35:20AM +0200, Tom van Tilburg wrote: > ERROR: function st_asgeojson(geometry) is not unique Sounds like an unclean upgrade (coexistance of old and new st_asgeojson signatures, one with default args, one without). Does loading the minor upgrade script fixes it ? What does SELECT postgis_full_version() tells you ? --strk; ,--o-. | __/ |Delivering high quality PostGIS 2.1 | / 2.1 |http://strk.keybit.net - http://vizzuality.com `-o--' ___ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
