Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with performance
Search options not deleted
user 136794
Performance is a subset of Optimization: performance is the goal when you want the execution time of your program or routine to be optimal.
0
votes
1
answer
51
views
Count buffered streets that intersect buffered points using PostGIS
PostgreSQL 9.5.1 with PostGIS 2.0 extension
This first section creates an intersection (clip) of the streets from another polygon (MTC15), then it buffers the intersection:
with cte_intersection a …
- 141
3
votes
Count buffered streets that intersect buffered points using PostGIS
adding this CTE decreased the time from 1 hr 11 minutes to 2 minutes 62 seconds:
cte_dumppoly as (select (st_dump(geom)).geom as geom, dccode from public."MTC15")
making the final query look like:
…
- 141