Hi Marc, This is very useful info.
Yes, I am using PostgreSQL 9.0 and yes, setting bytea_output = escape fixed the connection problems with FME. I'll pass this information on to Safe software if they aren't yet aware about the problem. Thanks a lot for the immediate and very useful answer! Andreas On Tue, July 27, 2010 1:14 pm, Mark Cave-Ayland wrote: > Andreas Neumann wrote: > >> Hi all, >> >> I recently installed Postgis-SVN (1.5.2SVN) together with PostgreSQL 9.0 >> beta 3 and noticed that FME (from Safe software) cannot read the >> geometries anymore. It used to work fine with older versions. >> >> The error message I get reads as follows: >> >> "Error in the OGR while importing well known binary geometry >> Invalid WKB encountered" >> >> I wonder if other users of Postgis SVN and FME are getting similar >> problems? > > Hi Andreas, > > If you're using PostgreSQL 9.0, you're probably getting affected by > this: http://trac.osgeo.org/postgis/ticket/538. > > In short, it seems that various applications don't use the official > PostgreSQL libpq unescape functions but instead implement their own - > and since the default representation has changed, the parsing code needs > to be updated. Note that you can change the default using the > bytea_output GUC in postgresql.conf if updating the software proves to > be impossible. > > > HTH, > > 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 > > Sirius Labs: http://www.siriusit.co.uk/labs > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > -- Andreas Neumann http://www.carto.net/neumann/ http://www.svgopen.org/ _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
