On 12/17/2010 11:37 AM, Robert Haas wrote:
On Fri, Dec 17, 2010 at 12:08 PM, Tom Polak <tom@xxxxxxxxxxxxxxxxxxxxxxxx> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
