PostgreSQL follows SQL compliance, as does MS SQL Server. 'complicated
queries' are left to the creativity of the SQL'er - squeler ;)
There are of course proprietary differences in 'enhancements.'
Some things that you can write in MS SQL, don't apply to Oracle/PostgreSQL/MySQL
and many permutations of the above comment amongst the varying RDBMS'.
On Mon, 13 Nov 2006, 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.
>
>
>
> Merlin Moncure-2 wrote:
>>
>> On 11/11/06, novnov <novnovice@gmail.com> wrote:
>>>
>>> I agree with what you say. And I'd still be interesting in hearing of
>>> first
>>> hand experience with the speed of the two databases from someone who is
>>> 'good' at both. The article commentor was obviously not a pgsql expert.
>>> I've
>>> heard recently that pgsql is as fast as mysql, so it seems odd that ms
>>> sql
>>> would be faster than pgsql. The actual test, what was use to benchmark,
>>> would make a difference of course.
>>
>> I have a ton of experience with postgresql and mysql, and a fair
>> amount with ms sql. Database performance is hard to nail down, it
>> means different things to different people. However, I it is my
>> personal opinion (backed up with hands-on experience) that PostgreSQL
>> has been pulling away from its major competitors in performance since
>> about 7.4 release. Actually, I think ms sql is a decent database and
>> it's a good choice if you like integration with ms tools. However,
>> like many products I think it topped out in value around year 2000 and
>> am not so sure about the current direction. Note that I only know
>> about yukon by what I've read about it.
>>
>> merlin
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 9: In versions below 8.0, the planner will ignore your desire to
>> choose an index scan if your joining column's datatypes do not
>> match
>>
>>
>
>
--
Louis Gonzales
louis.gonzales@linuxlouis.net
http://www.linuxlouis.net
