| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL versus MySQL for GPS Data |
| Date: | 2009-03-17 16:50:40 |
| Message-ID: | 1237308640.8159.31.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general |
On Tue, 2009-03-17 at 17:44 +0100, 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.
It entirely depends on workload and hardware.
Joshua D. Drake
>
> Thomas
>
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-03-17 17:03:39 | Re: PostgreSQL versus MySQL for GPS Data |
| Previous Message | Thomas Kellerer | 2009-03-17 16:44:48 | Re: PostgreSQL versus MySQL for GPS Data |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | adam.slachta | 2009-03-17 16:57:01 | Re: UPDATE of several columns using SELECT statement |
| Previous Message | Thomas Kellerer | 2009-03-17 16:44:48 | Re: PostgreSQL versus MySQL for GPS Data |