From: | "Ian Harding" <harding(dot)ian(at)gmail(dot)com> |
---|---|
To: | "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com> |
Cc: | novnov <novnovice(at)gmail(dot)com>, "pgsql general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Speed of postgres compared to ms sql, is this |
Date: | 2006-12-04 18:18:10 |
Message-ID: | 725602300612041018y5269031cp3f488042710ba865@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/13/06, Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
> On Mon, 2006-11-13 at 15:36, novnov wrote:
> > OK, thanks everyone, I gather from the responses that postgres performance
> > won't be an issue for me then. If MS SQL Server and Postgres are in the same
> > ballpark performance-wise, which seems to be the upshot of your comments, no
> > problem. I'd only have worried if there was something like the major
> > difference between the two with more complicated queries. I am puzzled by
> > the commentor's post to the article, it could be FUD of course but didn't
> > particularly sound like the commentor was anti pgsql.
>
> I will say this. Most other databases are more forgiving of bad
> queries. Make a bad query and postgresql is more likely to punish you
> for it.
Amen. When I migrated from MSSQL to PostgreSQL (4 years ago), I found
out exactly how seriously MS SQL coddles you when it comes to its "Oh,
I know what you really meant" query planning. I committed some sins
MS SQL covered up nicely and PostgreSQL flat out crawled when
presented to it.
However, I suspect that if I tried those bad queries with a current
version of PostgreSQL they would run much better, given all the work
that has been put in over the last few years.
- Ian
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Raia | 2006-12-04 18:18:16 | Install/Uninstall Issues |
Previous Message | brian | 2006-12-04 18:02:46 | Re: logs not ending up at Syslog |