<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16450"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=267154110-14112012>I don't see why we can't just enable it by default or
Paul -- if you really don't want it default make it a configuration
variable.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=267154110-14112012></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=267154110-14112012>Then it would be easy to have our buildbots just build
trunk with a different configure command. Fussing with .c files is much messier
since it requires changing source and remembering to change back if changes made
to the file (so too risky for buildbot testing).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=267154110-14112012></SPAN></FONT> </DIV>
<DIV><SPAN class=267154110-14112012></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT
size=2>I think for benchmarking comparing 2.0 behavior with new 2.1 will be sufficient.</FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT
size=2></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2>J<SPAN
class=267154110-14112012>ust my 2 cents,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=267154110-14112012>Regina</SPAN></FONT></FONT></FONT></DIV>
<DIV><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> postgis-devel-bounces@lists.osgeo.org
[mailto:postgis-devel-bounces@lists.osgeo.org] <B>On Behalf Of </B>Alexander
Korotkov<BR><B>Sent:</B> Wednesday, November 14, 2012 1:19 AM<BR><B>To:</B>
PostGIS Development Discussion<BR><B>Cc:</B> PostGIS Development
Discussion<BR><B>Subject:</B> Re: [postgis-devel] New node splitting algorithm
for GiST<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Paul,</DIV>
<DIV><BR></DIV>
<DIV>Who are expected to try it? I think in current state it's unlikely that
someone would try it until you ask him in person.</DIV>
<DIV><BR></DIV>Also, ITSM you selected extremely cautious strategy. It would be
reasonable to have a macro if we had some good algorithm of split before. For
example, split algorithm from R*-tree. But "New linear node splitting" sucks so
much...
<DIV><BR>------<BR>With best regards,<BR>Alexander Korotkov.<BR><BR>
<DIV class=gmail_quote>On Wed, Nov 14, 2012 at 2:14 AM, Paul Ramsey <SPAN
dir=ltr><<A href="mailto:pramsey@opengeo.org"
target=_blank>pramsey@opengeo.org</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>This is now on trunk, with a #define KOROTKOV_SPLIT
in<BR>gserialized_gist_2d.c to turn it on/off. Some extra testing (you
have<BR>to build a new index to get the new split in effect, just querying
an<BR>existing index will make no difference at all) to ensure we
have<BR>more/better performance would be great.<BR><BR><A
href="http://trac.osgeo.org/postgis/ticket/1895"
target=_blank>http://trac.osgeo.org/postgis/ticket/1895</A><BR><BR>P.<BR>
<DIV>
<DIV class=h5><BR>On Sun, Jul 1, 2012 at 8:00 AM, Alexander Korotkov <<A
href="mailto:aekorotkov@gmail.com">aekorotkov@gmail.com</A>> wrote:<BR>>
Done: <A href="http://trac.osgeo.org/postgis/ticket/1895"
target=_blank>http://trac.osgeo.org/postgis/ticket/1895</A><BR>><BR>>
------<BR>> With best regards,<BR>> Alexander Korotkov.<BR>><BR>>
On Sun, Jul 1, 2012 at 5:54 PM, Paragon Corporation <<A
href="mailto:lr@pcorp.us">lr@pcorp.us</A>> wrote:<BR>>><BR>>>
Alex,<BR>>><BR>>> Can you attach this to a ticket. That way
Paul won't forget or one of us<BR>>> can remind him when he does
:)<BR>>><BR>>> <A href="http://trac.osgeo.org/postgis/"
target=_blank>http://trac.osgeo.org/postgis/</A><BR>>><BR>>> Slate
it for 2.1.0<BR>>><BR>>> Thanks,<BR>>>
Regina<BR>>><BR>>> ________________________________<BR>>>
From: <A
href="mailto:postgis-devel-bounces@postgis.refractions.net">postgis-devel-bounces@postgis.refractions.net</A><BR>>>
[mailto:<A
href="mailto:postgis-devel-bounces@postgis.refractions.net">postgis-devel-bounces@postgis.refractions.net</A>]
On Behalf Of<BR>>> Alexander Korotkov<BR>>> Sent: Sunday, July 01,
2012 8:33 AM<BR>>> To: PostGIS Development Discussion<BR>>>
Subject: Re: [postgis-devel] New node splitting algorithm for
GiST<BR>>><BR>>> On Sat, Jun 30, 2012 at 10:59 PM, Paul Ramsey
<<A href="mailto:pramsey@opengeo.org">pramsey@opengeo.org</A>>
wrote:<BR>>>><BR>>>> No progress, still an "item of
interest" in my list of things I might<BR>>>> do. If you prepare a
compile-time conditional patch, I'd be interested<BR>>>> in reviewing
and applying it.<BR>>><BR>>><BR>>> OK, it's
here.<BR>>> Just an small example. Without
patch.<BR>>><BR>>> test=# create index geonames_idx on geonames
using gist (point);<BR>>> CREATE INDEX<BR>>> Time: 113796,848
ms<BR>>><BR>>> test=# explain (analyze, buffers) select * from
geonames where point &&<BR>>> 'BOX(34.4671 126.631,34.5023
126.667)'::box2d::geometry;<BR>>><BR>>> QUERY
PLAN<BR>>><BR>>>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>>
Index Scan using geonames_idx on geonames (cost=0.00..14.05
rows=2<BR>>> width=128) (actual time=0.589..0.876 rows=11
loops=1)<BR>>> Index Cond: (point &&<BR>>>
'0103000000010000000500000016FBCBEEC93B4140AAF1D24D62A85F4016FBCBEEC93B4140A69BC420B0AA5F40F163CC5D4B404140A69BC420B0AA5F40F163CC5D4B404140AAF1D24D62A85F4016FBCBEEC93B4140AAF1D24D62A85F40'::geometry)<BR>>>
Buffers: shared hit=26<BR>>> Total runtime: 0.927
ms<BR>>> (4 rows)<BR>>><BR>>> With
patch.<BR>>><BR>>> test=# create index geonames2_idx on geonames2
using gist (point);<BR>>> CREATE INDEX<BR>>> Time: 118382,076
ms<BR>>><BR>>> test=# explain (analyze, buffers) select * from
geonames2 where point &&<BR>>> 'BOX(34.4671 126.631,34.5023
126.667)'::box2d::geometry;<BR>>><BR>>><BR>>> QUERY
PLAN<BR>>><BR>>>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>>
Index Scan using geonames2_idx on geonames2 (cost=0.00..22.40
rows=4<BR>>> width=128) (actual time=0.209..0.225 rows=11
loops=1)<BR>>> Index Cond: (point &&<BR>>>
'0103000000010000000500000016FBCBEEC93B4140AAF1D24D62A85F4016FBCBEEC93B4140A69BC420B0AA5F40F163CC5D4B404140A69BC420B0AA5F40F163CC5D4B404140AAF1D24D62A85F4016FBCBEEC93B4140AAF1D24D62A85F40'::geometry)<BR>>>
Buffers: shared hit=11<BR>>> Total runtime: 0.276
ms<BR>>> (4 rows)<BR>>><BR>>> ------<BR>>> With best
regards,<BR>>> Alexander Korotkov.<BR>>><BR>>><BR>>>
_______________________________________________<BR>>> postgis-devel
mailing list<BR>>> <A
href="mailto:postgis-devel@postgis.refractions.net">postgis-devel@postgis.refractions.net</A><BR>>>
<A href="http://postgis.refractions.net/mailman/listinfo/postgis-devel"
target=_blank>http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>>><BR>><BR>><BR>>
_______________________________________________<BR>> postgis-devel mailing
list<BR>> <A
href="mailto:postgis-devel@postgis.refractions.net">postgis-devel@postgis.refractions.net</A><BR>>
<A href="http://postgis.refractions.net/mailman/listinfo/postgis-devel"
target=_blank>http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>><BR></DIV></DIV>_______________________________________________<BR>postgis-devel
mailing list<BR><A
href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</A><BR><A
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel"
target=_blank>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel</A><BR></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>