Kai Krueger schrieb:
Perhaps it can just use the keys that are in the standard osm2pgsql (plus perhaps the 10 most common name: tags) as columns and everything else in the hstore.
I would only keep the columns from the standard osm2pgsql style that are used for lookups. Eg. width, operator, ele can be dropped. but for the sake of simplicity we should just use the default osm2pgsql style so that we can keep the main mapnik-osm.
Do you know how performance compares between hstore and separate columns if your where clause doesn't touch the hstore, but the select pulls in data from there? The need for multiple accesses per data row might still slow things down, but that might not be a problem for features that are used less often.
I don't think this has a big impact. But as on the devderver we have a hstore-only import without extra columns I don't have timings for that.
Peter