From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Thomas Løcke <thomas(dot)granvej6(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL vs. Microsoft SQL server |
Date: | 2010-05-01 21:06:41 |
Message-ID: | m2ocgz2uxq.fsf@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Sat, May 1, 2010 at 2:47 PM, Thomas Løcke <thomas(dot)granvej6(at)gmail(dot)com> wrote:
>> Anybody know of any recent comparisons made between the two?
>>
>> I'm in the process of buying a new telephony related software suite,
>
> if you are writing stuff in C/C++, doing significant coding INSIDE the
> database (pl/pgsql, C, etc) and/or think of the database as a self
> contained development environment, then postgresql is definitely the
> right choice. our C interface (both libpq and internal) is excellent,
> variety of server side programming options is second to none, and
> postgres's flexible type system is fantastic and capable of doing all
> kinds of things that bend the rules of what a database is 'supposed to
> do'.
An specific example here would be the prefix_range data type that handle
indexing telephony routing queries. See it here:
http://prefix.projects.postgresql.org/
Keep in mind you'll find other side projects along with PostgreSQL to
help you answer to your business needs. It's not just about which is
faster on some random benchmark but which helps you best doing your
work.
I know nothing about MSSQL, but another axe of analysis that I tend to
follow is the error management. PostgreSQL is very good on this point,
you really can trust your data to it.
Regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2010-05-01 22:43:16 | Re: PostgreSQL vs. Microsoft SQL server |
Previous Message | Greg Smith | 2010-05-01 20:52:25 | Re: Native DB replication for PG |