From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
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-19 16:50:09 |
Message-ID: | dcc563d10903190950t235fd09ane4c0c8815c75804a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general |
On Tue, Mar 17, 2009 at 5:25 AM, Juan Pereira
<juankarlos(dot)openggd(at)gmail(dot)com> wrote:
> Hello,
>
> The question is: Which DBMS do you think is the best for this kind of
> application? PostgreSQL or MySQL?
Another advantage pgsql has is that many ddl operations on tables do
NOT require exclusive locks on those tables. Creating indexes, adding
/ dropping columns in mysql will lock the whole table and adding
dropping columns will rewrite the whole table. In pgsql adding and
dropping columns is almost immediate, and you can create indexes
concurrently so that the table you're creating the index on is not
locked. This is a big deal on a large production system where index
creation could take anywhere from several minutes to several hours.
Note that almost all ddl is transactable as well, so testing big
schema changes is much safer in pgsql, where you can rollback just
about anything except create / drop database / tablespace.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2009-03-20 01:37:35 | Re: PostgreSQL versus MySQL for GPS Data |
Previous Message | Brian Ghidinelli | 2009-03-19 16:05:15 | Re: [GENERAL] Re: [pgsql-advocacy] Video from the 2009-03-11 SFPUG talk on Unison, by Reese Hart |
From | Date | Subject | |
---|---|---|---|
Next Message | ANKITBHATNAGAR | 2009-03-19 16:53:31 | Special charaters |
Previous Message | Brian Ghidinelli | 2009-03-19 16:05:15 | Re: [GENERAL] Re: [pgsql-advocacy] Video from the 2009-03-11 SFPUG talk on Unison, by Reese Hart |