Changes between Version 15 and Version 16 of PostGISDevelopment2021


Ignore:
Timestamp:
08/20/21 10:35:48 (3 years ago)
Author:
pramsey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PostGISDevelopment2021

    v15 v16  
    3636= Meeting Notes =
    3737
    38  * TBD during the event
     38== Welcome ==
     39
     40 * Paul Ramsey (Crunchy Data) ... coordination towards release time in fall
     41 * Mahmoud SAKR (MobilityDB project, Université Libre de Bruxelles) - Discussing the dependancy of MobilityDB on PostGIS
     42 * Darafei Praliaskouski (Kontur) - XMeans and future of parallel things, H3 things and creation of extensions depending on main PostGIS
     43 * Regina (self)
     44 * Raúl Marín (self)
     45 * Mohamed Bakli (MobilityDB)
     46 * Brian M Hamlin - OSGeo Live DVD
     47 * Bruce Rindahl (self)  documentation
     48 * Giuseppe Broccolo - give updates about improvements in GiST build (with Han)
     49 * Han Wang - GiST with pre-sorting methods
     50 * Vicky Vergara (pgRouting & OSGeoLive & MobilityDB)
     51 * Maxime Schoemans (MobilityDB)
     52 * Esteban Zimanyi (MobilityDB)
     53 * Jignesh Shah (AWS) .. learning about PostGIS (More on managing multiple versions)
     54 * Aliaksandr Kalenik (Kontur)
     55
     56== Agenda ==
     57
     58 * GSOC Gist building enhancements for PostgreSQL 14
     59 * Need for a postgis_c_api for projects like MobilityDB, h3_pg
     60 * PostGIS 3.2 ticket triage
     61 * Real World data testing
     62 * Vote: Should our master repo be master or main?
     63
     64== GIST Building GSOC Project ==
     65
     66 * Good PoC completed
     67 * Uses Pg14 pre-sort hooks in GIST to speed index build
     68 * Index build time is made much faster
     69 * Query performance may be slightly (?) degraded compared to old implementation w/o pre-sort
     70 * Pre-sort changes low-level page composition a little bit deleteriously
     71 * Need some feedback on query against real-world data sets
     72 * Is the sort key length (32bit) the problem? (Maybe not? Datum size is 64bit on most hardware)
     73 * Q: Do PgSQL implementations of presort also show a performance degredation in query?
     74 * Some degradation is expected. check first: https://observablehq.com/@mourner/hilbert-curve-packing
     75
     76== postgis_c_api ==
     77
     78 * MobilityDB uses liblwgeom library since PostGIS ~2.3 but can't support 3.x as liblwgeom is not exported
     79 * MobilityDB uses a lot of functions in geography and other analytical functions, not just serialize/deserialize/lwgeom
     80 * LWGEOM is done because Spatialite needed the topology
     81 * Q: Can we provide an example of a "dependent extension" that calls PostGIS functions directly?
     82 * VVergara will continue examining the actual extent of dependency and we will revisit
     83 * Q: Call out pgpointcloud example of non-binary extension dependency
     84 *  https://en.wikipedia.org/wiki/GPL_linking_exception#:~:text=A%20GPL%20linking%20exception%20modifies,GPL%20to%20the%20using%20program.
     85
     86== master or main ==
     87
     88 * master - PR, Regina +1, Giuseppe, MS, Darafei +0  BH +1,JeremyVicky -0
     89 * main  -  BR, Regina -1, Darafei +1,Jignesh  Vicky +0
     90 * Don't care: RM, Darafei +1 MD for now, but plan should be to change to main
     91
     92== Real World Data Testing ==
     93
     94 * Regina setting up a testing infrastructure
     95 * Real world data sets in the "real" folder
     96 * Example: https://github.com/pramsey/geos-performance/
     97
     98== PostGIS 3.2 Ticket Triage ==
     99
     100* https://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reopened&milestone=PostGIS+3.2.0&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority
     101
     102== Alpha Release ==
     103
     104Dependent on
     105 * Han's GIST sort merge
     106 * KMeans merge
     107 * Boundary merge
     108 * Paul's three feature tickets
     109 * Paul's crasher tickets
     110 * Sandro's cleanup of topology tickets and feature completion
     111 * Upgrade changes (Regina)
     112 * Address standardizer (Regina)
     113
     114Target date?
     115 * August 34th
     116
     117== Next Meeting? ==
     118
     119 * Maybe pre-release 3.2?
     120 * For sure mid-winter (Jan/Feb?) + 1