From: | Alex Turner <armtuk(at)gmail(dot)com> |
---|---|
To: | Jan <janoleolsen(at)hotmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL vs mySQL, any performance difference for large queries? |
Date: | 2005-10-24 21:26:26 |
Message-ID: | 33c6269f0510241426t22bb3d82p9b8c3d005ed707df@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I would ask you to ask the reverse question, why would you use MySQL when it
still doesn't contain all the features of postgresql, has a bad query
optimizer, a poor track record on scalability and will silenty
truncate/accept invalid data, invalidating ACID, not only that you have to
pay for it.
Why would you use MySQL?
Alex
On 24 Oct 2005 13:37:23 -0700, Jan <janoleolsen(at)hotmail(dot)com> wrote:
>
> I need a database capable of storing at least 12 million records per
> table, mostly used for batch queries. Basically an invoice database.
> Some tables could potentially store 100 million records.
>
> mySQL5 contains many of the features or PostgreSQL, and I doubt that I
> need all these features. Are there any spefic benefits in query
> performance or reliability of going with PostgreSQL?
>
> Secondary need is a database where 200 users will need to perform
> lookups, probably using Windows PC's. Most likely only a handful will
> perform lookups simultanously.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Brent Wood | 2005-10-24 21:28:54 | Re: Map of Postgresql Users (OT) |
Previous Message | Alex Turner | 2005-10-24 21:21:00 | Re: a stored procedure ..with integer as the parameter |