| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL versus MySQL for GPS Data |
| Date: | 2009-03-17 16:44:48 |
| Message-ID: | gpok21$jad$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy 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 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-03-17 16:50:40 | Re: PostgreSQL versus MySQL for GPS Data |
| Previous Message | Erik Jones | 2009-03-17 16:05:15 | Re: PostgreSQL versus MySQL for GPS Data |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-03-17 16:50:40 | Re: PostgreSQL versus MySQL for GPS Data |
| Previous Message | Erik Jones | 2009-03-17 16:05:15 | Re: PostgreSQL versus MySQL for GPS Data |