[postgis-devel] Call for 1.4.2 and 1.5.1
strk
strk at keybit.net
Mon Feb 15 14:01:27 PST 2010
Dear spatial DB angles,
this is a call for 1.4.2 and 1.5.1 releases due
to impossibility to hard-upgrade 1.4.1 and 1.5.0
in some situations.
In detail: if you imported geometries from
a malformed shapefile there'll be NO WAY to get
those geometries out due to over-anal^Wstrict
behaviour of the unparser.
Here's an example:
# create table bug (g geometry);
# insert into bug values ('0103000000010000000300000000000000000000000000000000000000000000000000F03F000000000000F03F000000000000F03F000000000000F03F0000000000000000');
# select summary(g) from bug;
Polygon[B] with 1 rings
ring 0 has 3 points
Now your geometry is IN and can't get out:
# select g from bug;
ERROR: geometry contains non-closed rings
# copy bug to '/tmp/out';
ERROR: geometry contains non-closed rings
Can't backup - upgrade :
$ pg_dump -t bug postgis_bug_14
pg_dump: SQL command failed
pg_dump: Error message from server:
ERROR: geometry contains non-closed rings
pg_dump: The command was: COPY public.bug (g) TO stdout;
So, bottom line: the patch is already in 1.4 and 1.5 branches, the
sooner we'll get 1.4.2 and 1.5.1 out the least problem people will
have upgrading later.
Would also be worth adding the critical shapefile to the regression
to check symmetric in-out as with all the other ones.
--strk;
() Free GIS & Flash consultant/developer
/\ http://foo.keybit.net/~strk/services.html
More information about the postgis-devel
mailing list