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

From Harald Armin Massa
Subject Re: PostgreSQL versus MySQL for GPS Data
Date
Msg-id e3e180dc0903170700v27c4e7j374b37f9d06895a5@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL versus MySQL for GPS Data  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: PostgreSQL versus MySQL for GPS Data  (Thomas Kellerer <spam_eater@gmx.net>)
Re: PostgreSQL versus MySQL for GPS Data  (Merlin Moncure <mmoncure@gmail.com>)
Re: PostgreSQL versus MySQL for GPS Data  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
List pgsql-general
Merlin,

> I agree though
> that a single table approach is best unless 1) the table has to scale
> to really, really large sizes or 2) there is a lot of churn on the
> data (lots of bulk inserts and deletes).

while agreeing, an additional question: could you please pronounce
"really, really large" in other units, like Gigabytes or Number of
rows (with average rowlength in bytes, of course)

That is: what table size would you or anybody consider really, really
large actually?

Harakd


--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
LASIK good, steroids bad?

pgsql-general by date:

Previous
From: Erik Jones
Date:
Subject: Re: PostgreSQL versus MySQL for GPS Data
Next
From: Thomas Kellerer
Date:
Subject: Re: PostgreSQL versus MySQL for GPS Data