[postgis-devel] geos / postgis version
strk at keybit.net
Fri Jul 23 15:10:26 PDT 2004
I've added postgis_proj_version() function, so we now have:
postgis_lib_version(); -- reports version of postgis lib
postgis_geos_version(); -- reports version of GEOS lib (or NULL)
postgis_proj_version(); -- reports version of PROJ lib (or NULL)
These 3 functions should give complete library capabilities
Now. Common problem is that you used postgis.sql from an older
postgis release and you upgraded only the library. This can now
be detected. The function postgis_version() is an 'sql' function
so it will NOT depend on libpostgis. This function reports:
- wheter GEOS has been enabled.
- wheter PROJ has been enabled.
- postgis release the enabler came from.
We should find out when a postgis function definition set
(postgis.sql) is incompatible with the postgis library or
just old in respect to the library.
Actually there are currently no cases of incompatibility
AFAIK, but more often you have a bogus 'sql' file and a good
library. We could assign a version number to the 'sql'
file, and have two functions report it: an 'sql' function
and a 'C' function. Comparing the two will give us an hint
On Thu, Jul 22, 2004 at 07:12:09PM +0200, strk wrote:
> Ok, geos::version() has been split in geos::geosversion()
> and geos::jtsport().
> Postgis postgis_geos_version() will report geos version only
> (I don't think we need to know JTS equivalent...)
> I won't make the postgis_scripts_version() function now, as
> I think it requires a deeper though about how it is supposed
> to be used... If we need it to detect an incongruency between
> pl/pgsql,sql functions and library functionalities we need to
> understand what makes an incongruency and what does not.
> On Thu, Jul 22, 2004 at 06:20:45PM +0200, strk wrote:
> > I've added postgis_lib_version() and postgis_geos_version().
> > Before proceeding it might be worth changing geos::version()
> > output (and maybe name) to be able to get GEOS version only
> > (and geos::jtsport() addition...).
> > Any hint on proj4 version string extraction is appreciated
> > (with back-compatibility in mind).
> > NOTE that postgis_lib_version also reports micro version
> > which is actually not used in library file name (this is
> > built using postgresql rule, which do not take a micro version
> > number). Remember to upgrade SO_MICRO_VERSION between releases.
> > --strk;
> > On Thu, Jul 22, 2004 at 08:24:59AM -0700, Paul Ramsey wrote:
> > > I think it is wise, and you should look at one of the emails today,
> > > which suggested reporting out versions of the libraries we are using
> > > (geos,proj) in addition to whether we have them.
> > >
> > > strk wrote:
> > > >Current postgis_version() function is implemented as a pl/pgsql
> > > >function. Sometimes people upgrade postgis library w/out upgrading
> > > >pl/pgsql functions, and this is *sometimes* a problem.
> > > >
> > > >I think it would be useful to have the following informations
> > > >retrivable:
> > > > postgis_scripts_version(); // pl/pgsql function
> > > > postgis_lib_version(); // C function
> > > > postgis_geos_version(); // C function
> > > >
> > > >Our postgis_version() would then be a wrapper, retriving the above
> > > >informations and warning user in case
> > > >postgis_scripts_version() != postgis_lib_version()
> > > >
> > > >What do you think ?
> > > >
> > > >--strk;
> > > >_______________________________________________
> > > >postgis-devel mailing list
> > > >postgis-devel at postgis.refractions.net
> > > >http://postgis.refractions.net/mailman/listinfo/postgis-devel
> > >
> > > _______________________________________________
> > > postgis-devel mailing list
> > > postgis-devel at postgis.refractions.net
> > > http://postgis.refractions.net/mailman/listinfo/postgis-devel
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-devel
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
More information about the postgis-devel