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

From Thomas Kellerer
Subject Re: PostgreSQL versus MySQL for GPS Data
Date
Msg-id gpok21$jad$1@ger.gmane.org
Whole thread Raw
In response to Re: PostgreSQL versus MySQL for GPS Data  (Harald Armin Massa <chef@ghum.de>)
Responses Re: PostgreSQL versus MySQL for GPS Data  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: PostgreSQL versus MySQL for GPS Data  (Sam Mason <sam@samason.me.uk>)
Re: PostgreSQL versus MySQL for GPS Data  (Shane Ambler <pgsql@Sheeky.Biz>)
List pgsql-general
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
whenthe 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

pgsql-general by date:

Previous
From: Harald Armin Massa
Date:
Subject: Re: PostgreSQL versus MySQL for GPS Data
Next
From: "Joshua D. Drake"
Date:
Subject: Re: PostgreSQL versus MySQL for GPS Data