From: | Andy Colson <andy(at)squeakycode(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Polak <tom(at)rockfordarearealtors(dot)org>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Compared MS SQL 2000 to Postgresql 9.0 on Windows |
Date: | 2010-12-17 17:50:03 |
Message-ID: | 4D0BA2CB.3090809@squeakycode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 12/17/2010 11:37 AM, Robert Haas wrote:
> On Fri, Dec 17, 2010 at 12:08 PM, Tom Polak
> <tom(at)rockfordarearealtors(dot)org> wrote:
> other direction to get good performance, too. You're not going to
> compare two major database systems across the board and find that one
> of them is just twice as fast, across the board. They have different
> advantages and disadvantages. When you're using one product, you
> naturally do things in a way that works well for that product, and
> moving to a different product means starting over. Oh, putting this
> in a stored procedure was faster on MS SQL, but it's slower on
> PostgreSQL. Using a view here was terrible on MS SQL, but much faster
> under PostgreSQL.
>
Yeah, totally agree with that. Every database has its own personality,
and you have to work with it. Its way. Dont expect one bit of code to
work great on all the different databases. You need 5 different bits of
code, one for each database.
In the end, can PG be fast? Yes. Very. But only when you treat is as
PG. If you try to use PG as if it were mssql, you wont be a happy camper.
-Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pitts | 2010-12-17 19:53:48 | Re: Compared MS SQL 2000 to Postgresql 9.0 on Windows |
Previous Message | Tom Polak | 2010-12-17 17:49:42 | Re: Compared MS SQL 2000 to Postgresql 9.0 on Windows |