Re: PostgreSQL versus MySQL for GPS Data - Mailing list pgsql-general

From Shane Ambler
Subject Re: PostgreSQL versus MySQL for GPS Data
Date
Msg-id 49C265F6.7080703@Sheeky.Biz
Whole thread Raw
In response to Re: PostgreSQL versus MySQL for GPS Data  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: PostgreSQL versus MySQL for GPS Data
List pgsql-general
Thomas Kellerer wrote:
> Harald Armin Massa, 17.03.2009 15:00:
>> That is: what table size would you or anybody consider really,
>> really large actually?
>
> I recently attended and Oracle training by Tom Kyte and he said
> (partially joking though) that a database is only large when the size
> is measured in terrabytes :) So really, really large would mean
> something like 100 petabytes
>
>
> My personal opinion is that a "large" database has more than ~10
> million rows in more than ~10 tables.
>
> Thomas
>
>
I would say that as far as GPS data goes the street maps of the world
would be pretty big.

openstreetmap.org is still a work in progress but their current db dumps
gzip down to 6.4GB. It was a while back that I noseyed around with it
but I do recall that it compressed well and was very large uncompressed.
Don't recall how many rows it contained.

I wonder what an almost complete world street map like google maps comes
in at?



--

Shane Ambler
pgSQL (at) Sheeky (dot) Biz


pgsql-general by date:

Previous
From: "Marcelo Giovane"
Date:
Subject: Comando USE
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Maximum transaction rate