[postgis-devel] Bug in default B-Tree operator class for geography

[Darafei "Komяpa" Praliaskouski]

What happens on LINESTRING EMPTY < POINT EMPTY?

Also, ordering in geohash / z-curve would make many spots where it's used a
lot more efficient :)

пн, 11 сент. 2017 г. в 17:31, Paul Ramsey <pramsey at cleverelephant.ca>:

> I took a stab at it in https://trac.osgeo.org/postgis/ticket/3841
>
> Any spelunk into the b-tree side re-raises questions about "what do we
> mean by equal" and "how should we sort", making we want to tear off the
> bandages and try again.
>
> On Sun, Sep 10, 2017 at 5:05 PM, Peter Geoghegan <pg at bowt.ie> wrote:
>
>> Hi Paul,
>>
>> On Wed, Aug 24, 2016 at 8:25 AM, Paul Ramsey <pramsey at cleverelephant.ca>
>> wrote:
>> > Thanks for this Peter.
>> > Fortunately b-tree opclasses on geom/geog are but rarely used and even
>> more
>> > rarely build into actual indexes, since they don't provide any useful
>> > spatial searching capability.
>>
>> When do you expect to get around to fixing this? With amcheck in
>> Postgres 10, I would expect more people to notice this.
>>
>> Thanks
>> --
>> Peter Geoghegan
>>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20170911/b82c90e2/attachment.html>