<div dir="ltr"><div>Hi Paul,</div><div><br></div><div>I have a question: I see you used the function `gist_stat` to inspect the GiST indexes which is quite useful to check the overlaps between the boxes in the leaf nodes. I would like to use it as well,</div><div>but unfortunately I wasn't able to find any reference beside the <a href="http://www.sai.msu.su/~megera/wiki/Gevel">gevel repo</a>. Could you tell me which extension you used to get this function?</div><div><br></div><div>Thanks in advance,</div><div>Giuseppe.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno mar 11 gen 2022 alle ore 21:17 Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> On Jan 11, 2022, at 12:52 PM, Giuseppe Broccolo <<a href="mailto:g.broccolo.7@gmail.com" target="_blank">g.broccolo.7@gmail.com</a>> wrote:<br>
> <br>
> Hi Darafei,<br>
> <br>
> On Sun, 9 Jan 2022, 14:12 Darafei "Komяpa" Praliaskouski, <<a href="mailto:me@komzpa.net" target="_blank">me@komzpa.net</a>> wrote:<br>
> Hi everyone,<br>
> <br>
> After several weeks of research, testing and experiments we believe we found a solution that does not cause the select performance degradation (or sometimes brings profit) and still builds the index faster using the sorting build method. <br>
> <br>
> The patch is posted on pgsql-hackers by Aliaskandr Kalenik in this thread:<br>
> <br>
> <a href="https://www.postgresql.org/message-id/CAHqSB9jqtS94e9%3D0vxqQX5dxQA89N95UKyz-%3DA7Y%2B_YJt%2BVW5A%40mail.gmail.com" rel="noreferrer" target="_blank">https://www.postgresql.org/message-id/CAHqSB9jqtS94e9%3D0vxqQX5dxQA89N95UKyz-%3DA7Y%2B_YJt%2BVW5A%40mail.gmail.com</a><br>
> <br>
> Patch on commitfest:<br>
> <br>
> <a href="https://commitfest.postgresql.org/36/3487/" rel="noreferrer" target="_blank">https://commitfest.postgresql.org/36/3487/</a><br>
> <br>
> Sergei Shoulbakov implemented the benchmark to prove the effect. Results and notes are posted here:<br>
> <a href="https://www.postgresql.org/message-id/3aa6ba30-e9d8-10ef-753f-8deea5f196d0%40kontur.io" rel="noreferrer" target="_blank">https://www.postgresql.org/message-id/3aa6ba30-e9d8-10ef-753f-8deea5f196d0%40kontur.io</a><br>
> <br>
> We need your help to get it reviewed and merged to get the benefits for everyone in PG15. <br>
> <br>
> That's cool! What can we do to help?<br>
<br>
Well, one thing we definitely need is to compare the performance of the patched sortsupport method to the vanilla index build, across a variety of inputs and workloads. My example data was interesting, as a heterogenous set of data (differing object spatial sizes, differing densities across the data set) but there's lot of other different data that should be benchmarked. Get your favourite data sets and see what happens. Tests on small tables might also have some quirks that don't show up in large table tests. Harder to measure, but worth measuring.<br>
<br>
ATB,<br>
P<br>
<br>
<br>
> <br>
> Giuseppe. <br>
> _______________________________________________<br>
> postgis-devel mailing list<br>
> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
<br>
_______________________________________________<br>
postgis-devel mailing list<br>
<a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
</blockquote></div>