From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Juan Pereira <juankarlos(dot)openggd(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL versus MySQL for GPS Data |
Date: | 2009-03-17 15:54:51 |
Message-ID: | 20090317155451.GI8123@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general |
Juan,
* Juan Pereira (juankarlos(dot)openggd(at)gmail(dot)com) wrote:
> The main reason why we thought using a table per truck was because
> concurrent load: if there are 100 trucks trying to write in the same table,
> maybe the performance is worse than having 100 tables, due to the fact that
> the table is blocked for other queries while the writing process is running,
> isn't it?
That assumption is incorrect with regard to PostgreSQL, as you'll find
if you go through the other links suggested. Writing to a table does
not require a table-level write lock in PostgreSQL.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2009-03-17 16:05:15 | Re: PostgreSQL versus MySQL for GPS Data |
Previous Message | Craig Ringer | 2009-03-17 15:11:30 | Re: PostgreSQL versus MySQL for GPS Data |
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2009-03-17 15:59:36 | Re: Running Postgresl in a virual machine |
Previous Message | Bill Moran | 2009-03-17 15:53:09 | Re: Running Postgresl in a virual machine |