Re: [Fwd: Question] - Mailing list pgsql-advocacy

From Josh Berkus
Subject Re: [Fwd: Question]
Date
Msg-id 200304231950.16570.josh@agliodbs.com
Whole thread Raw
In response to [Fwd: Question]  (Justin Clift <justin@postgresql.org>)
List pgsql-advocacy
Mr. Thibodeau,

> **
> *Hello.

Hello.  I'm Josh Berkus.  As a consultant, I administrate both PostgreSQL and
MS SQL Server profesionally, so I decided to take your question.

> We are considering using Postgre SQL over SQL server.

That's a good first step on the road to freedom from restrictive software
licensing.

> We need
> the trigger*
> *capability.

Which makes PostgreSQL a very good choice.  Between Postgres' multiple
function languages and flexible triggers, and the RULE query-rewriting
system, PostgreSQL  has the most powerful and flexible system for database
automation of any database, period.

Between MS SQL and Postgres, there is no contest.   For me, it is always
horribly frustrating whenever I have to write triggers in MS SQL.

 > However, I am told by a few programmers that Postgre
> operated slower*
> *than say SQL server or other database solutions in the same category.*
> **
> *First, is there any thruth to this?

No, none whatsoever.

MS SQL does a few things faster than PostgreSQL, primarily aggregate querys.
PostgreSQL does more than a few things faster than MS SQL Server, especially
on very low-end and very high-end hardware.

> (We are assuming that all platforms run on all the same servers, hence
> have access*
> *to all the same amount of memory and processing power).*

PostgreSQL's Windows port is still being tested.  If your primary goal is
performance, I strongly recommend that you test PostgreSQL on BSD, Linux, or
mainframe Unix.

Good luck on your evaluation.

--
Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-advocacy by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Slashdot article -OSNews
Next
From: "Dave Page"
Date:
Subject: Re: [webmaster] Case Studies Examining its Use [Dravis, 2003]