On Thu, Aug 9, 2012 at 2:42 PM, Flavio Curella <flavio.cure...@gmail.com> wrote: > From the benchmark, my understanding is that, on PostGIS 2.0: > > 1) for the 2D case, the best index is 'gist (columname)' > 2) for the 3D case, the best index is 'gist (columname > gist_geometry_ops_nd)' only when using specific 3D operators (ie: '&&&') > > I think we should create the index for 2D case, just as we did on PostGIS > 1.5. > > Re: the 3D case, 2) brings the question: should we add these new operators? > Is it out of scope for the ticket?
I think we clearly should, but landing basic support now and adding new operators later is also useful. Thanks for doing this work, by the way. :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
