[Tile-serving] [osm2pgsql] Partitioning (#92)
Paul Norman
notifications at github.com
Fri Oct 4 11:42:03 UTC 2013
yes, for a table partitioned into tbl_1 and tbl_2 and a where condition unrelated to the partition, the query is equivalent to `SELECT ... FROM tbl_1 WHERE ... UNION ALL SELECT ... FROM tbl_2 WHERE ...;`. I've been advised that with the table sizes involved in OSM, a couple of partitions won't add significant overhead.
I also believe that if the distribution of *other* values within the two partitions varies significantly and those values are indexed and used in queries there can be benifits.
I might have a try at doing a test with manually partitioning an existing import to see what gains can be achieved.
---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/92#issuecomment-25692865
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20131004/b3dc1ceb/attachment.html>
More information about the Tile-serving
mailing list