I agree - my approach is the playground approach: At first, keep it simple. For your purpose it is
correct to split the table. What about a partial index over 1 table? This is possible with Postgres.
Am 19.11.10 11:03, schrieb Sven Geggus:
Andreas Kalsch<[email protected]> wrote:
Example for unnessessary complex schema design:
http://wiki.openstreetmap.org/wiki/DE:HowTo_minutely_hstore
You are welcome to design a better database scheme suitable for rendering :)
osm2pgsql output is evolution _not_ design.
Using a join in every single SQL request is not an Option in this case at
least performancewise.
Probably I am wrong ... yes I know that you can index hstore with a GIST.
GIN
Sven
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev
