[OSM-dev] PostgreSQL vs HSQL

[Marcus Wolschon]

On Tue, Aug 11, 2009 at 12:24 AM, Michael Handerek<osm at handerek.net> wrote:
> Hi,
>
> I am still working on a reverse geocoding solution and had a look at
> traveling salseman's navigation subsystems. The advanced place finder
> for example uses HSQL instead of PostgreSQL, are there significant
> performance differences? Or is this decision only caused SVMby the
> lightness of the HSQL implementation?

Actually the SVN-Version moved from Hsql to the newer H2 (Hsql still supported).
The advantage is that:
a) As an embedded database in a program for end-users the user is not forced
to install PostgreSQL
b) It is very very small on disk and very fast.

Having a clueless end-user install PostgreSQL e.g. on a Windows Netbook
is not an option.

Also the PostgreSQL-Schema used by other tools here is of little use to us
as we found that we
a) NEED to have 3 additional, simplified maps in order to zoom out and still
    render a city, country, continent in real time
b) the "usual" schema is geared towards editors requesting areas and routers
    using only postGIS with it`s limited metrics and algorithms while
    we have a completely different access patterns.

However IbrahimB seems to work on PostgreSQL-support.
https://sourceforge.net/apps/phpbb/travelingsales/viewtopic.php?f=5&t=94

>
>
> Regards, mic
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>