Re: [OSM-dev] hstore / db schema Was: Query-Formats

2010-03-26 Thread Peter Körner
Brett Henderson schrieb:
> I am currently building most of my applications around the osmosis
> db schema but the split into node and node_tags and way and way_tags
> is - hum - not very efficient.
> 
> The current schema is fairly naive in its implementation.  I hadn't 
> heard of hstore when implementing it.  Perhaps the current schema needs 
> an upgrade :-)


I'd suggest collecting more info about hstore-performance before 
changing anything. We're on the planet.import on dev-server and there's 
also a ticket open to get hstore-new to the wikimedia toolservers. There 
you can play with it and test its performance and if it's good then we 
should definitely give it a try!

Peter

___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev


Re: [OSM-dev] hstore / db schema Was: Query-Formats

2010-03-26 Thread Brett Henderson
On Thu, Mar 25, 2010 at 3:42 AM, Florian Lohoff  wrote:

> On Tue, Mar 23, 2010 at 01:30:04PM +0100, Peter Körner wrote:
> > Hi
> >
> > On the osm dev-server we're playing around with the postgres-hstore
> > extension which allows us to repond to xapi-like queries, but with
> > already assembled LIESTRINGs and such neat things.
>
> Which is not per se a feature of hstore ... hstore is just another
> data type which is neat because it fits into the OSM model concerning
> tags ...
>
> I am currently building most of my applications around the osmosis
> db schema but the split into node and node_tags and way and way_tags
> is - hum - not very efficient.
>

The current schema is fairly naive in its implementation.  I hadn't heard of
hstore when implementing it.  Perhaps the current schema needs an upgrade
:-)


> This is why i would be interested in some tools to import a planet/sub
> extract
> into a more efficient db scheme which still allows to store all details
> of the osm planet (which osm2pgsql does not) but is more efficient
> concerning spatial queries.
>
> E.g. i'd like to drop way_tags and put them into a hstore tags column in
> the
> way table and then cluster the way table with the geom index on the
> linestring
> for example.
>
> Does anyone have speed/place comparisons?
>
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev


[OSM-dev] hstore / db schema Was: Query-Formats

2010-03-24 Thread Florian Lohoff
On Tue, Mar 23, 2010 at 01:30:04PM +0100, Peter Körner wrote:
> Hi
> 
> On the osm dev-server we're playing around with the postgres-hstore 
> extension which allows us to repond to xapi-like queries, but with 
> already assembled LIESTRINGs and such neat things.

Which is not per se a feature of hstore ... hstore is just another
data type which is neat because it fits into the OSM model concerning 
tags ... 

I am currently building most of my applications around the osmosis 
db schema but the split into node and node_tags and way and way_tags
is - hum - not very efficient.

This is why i would be interested in some tools to import a planet/sub extract
into a more efficient db scheme which still allows to store all details
of the osm planet (which osm2pgsql does not) but is more efficient
concerning spatial queries.

E.g. i'd like to drop way_tags and put them into a hstore tags column in the
way table and then cluster the way table with the geom index on the linestring
for example.

Does anyone have speed/place comparisons?

Flo
-- 
Florian Lohoff f...@zz.de
"Es ist ein grobes Missverständnis und eine Fehlwahrnehmung, dem Staat
im Internet Zensur- und Überwachungsabsichten zu unterstellen."
- - Bundesminister Dr. Wolfgang Schäuble -- 10. Juli in Berlin 


signature.asc
Description: Digital signature
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev