Your message dated Thu, 13 Sep 2018 16:36:18 +0200 with message-id <[email protected]> and subject line Re: Bug#908731: postgis: Normal query can fail with "index returned tuples in wrong order" error has caused the Debian Bug report #908731, regarding postgis: Normal query can fail with "index returned tuples in wrong order" error to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 908731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908731 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: postgis Version: 2.3.1+dfsg-2 Severity: normal Tags: upstream Dear Maintainer, Version 2.3.1 of postgis has a bug whereby geometry queries can sometimes fail. For example: mapit=# create table test (geo geometry); CREATE TABLE mapit=# insert into test values mapit-# ('0101000020E61000007D91D0967329E4BF6631B1F9B8D64A40'::geometry), mapit-# ('0101000020E6100000E2AFC91AF510C1BFCDCCCCCCCCAC4A40'::geometry); INSERT 0 2 mapit=# create index on test using gist (geo); CREATE INDEX mapit=# vacuum analyze test; VACUUM mapit=# set enable_seqscan = false; SET mapit=# select * from test ORDER BY geo::geometry <-> mapit-# ('0101000020E610000092054CE0D6DDE5BFCDCCCCCCCCAC4A40'::geometry); ERROR: index returned tuples in wrong order mapit=# drop table test; DROP TABLE mapit=# This was reported upstream at: https://trac.osgeo.org/postgis/ticket/3418 And fixed in postgis 2.3.2, the 2.3 commit fixing it is here: https://trac.osgeo.org/postgis/changeset/15285 Is there any chance this could be included/backported to fix the issue in stretch? ATB, Matthew -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/28 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgis depends on: ii libc6 2.24-11+deb9u3 ii libgdal20 2.1.2+dfsg-5 ii libgeos-c1v5 3.5.1-3 ii liblwgeom-2.3-0 2.3.1+dfsg-2 ii libpq5 9.6.10-0+deb9u1 Versions of packages postgis recommends: ii postgis-doc 2.3.1+dfsg-2 ii postgresql-9.6-postgis-2.3 2.3.1+dfsg-2 Versions of packages postgis suggests: pn postgis-gui <none> -- no debconf information
--- End Message ---
--- Begin Message ---tags 908731 wontfix thanks Hi Matthew, On 9/13/18 10:19 AM, Matthew Somerville wrote: > Version 2.3.1 of postgis has a bug whereby geometry queries can sometimes > fail. > For example: > > [...] > > This was reported upstream at: https://trac.osgeo.org/postgis/ticket/3418 > And fixed in postgis 2.3.2, the 2.3 commit fixing it is here: > https://trac.osgeo.org/postgis/changeset/15285 > > Is there any chance this could be included/backported to fix the issue > in stretch? The severity of this issue needs to be important or higher to be eligible for a stable update. The upstream issue is classified as medium, which doesn't seem severe enough to increase the severity of this bugreport to important unfortunately. I suggest you cherry-pick the upstream commit and include it as a patch in an unofficial update of the stretch package to host in your own apt repository. Kind Regards, Bas
--- End Message ---
_______________________________________________ Pkg-grass-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
