Difference between revisions of "Paris Code Sprint 2016 : PostGIS Agenda"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | Discussion and group review topics for the [Paris Code Sprint 2016]. | ||
| + | |||
| + | == Discussion == | ||
| + | |||
* Clustering functions: Aggregate or Window? | * Clustering functions: Aggregate or Window? | ||
** What naming convention | ** What naming convention | ||
| Line 17: | Line 21: | ||
** Parallel query, review experiments, plan and execute more | ** Parallel query, review experiments, plan and execute more | ||
** Feed back parallel query results to pgsql-hackers | ** Feed back parallel query results to pgsql-hackers | ||
| + | |||
| + | == Tasks == | ||
| + | |||
| + | * Benchmarking of expanded object headers test branch | ||
| + | * Benchmarking of parallel query and parallel aggregate work from pgsql-hackers | ||
Revision as of 06:27, 21 January 2016
Discussion and group review topics for the [Paris Code Sprint 2016].
Discussion
- Clustering functions: Aggregate or Window?
- What naming convention
- What to do with the existing aggregate functions
- Expanded object headers, introduction and testing
- How they work
- Potential advantages, disadvantages
- Discussion on clean implementation possibilities
- Testing and benchmarks, is it worth it?
- Alternate storage formats, beyond GSERIALIZED
- Reasoning
- How to add (version flags?)
- Multiple co-existing formats?
- Breaking raster out as postgis_raster extension
- Implications / difficulties
- GEOS improvements that would help PostGIS
- PostgreSQL improvements that would help PostGIS
- Parallel query, review experiments, plan and execute more
- Feed back parallel query results to pgsql-hackers
Tasks
- Benchmarking of expanded object headers test branch
- Benchmarking of parallel query and parallel aggregate work from pgsql-hackers