Search Postgresql Archives

Re: "Too far out of the mainstream"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-
> owner@xxxxxxxxxxxxxx] On Behalf Of Andy Yoder
> Sent: Friday, August 31, 2012 3:25 PM
> To: pgsql-general@xxxxxxxxxxxxxx
> Cc: Andy Yoder
> Subject:  "Too far out of the mainstream"
> 
> Hello all,
> 
> I would like the community's input on a topic.  The words "too far out of
the
> mainstream" are from an e-mail we received from one of our clients,
> describing the concern our client's IT group has about our use of
PostgreSQL
> in our shop.  The group in question supports multiple different databases,
> including Oracle, MySQL, SQLServer, DB2, and even some non-relational
> databases (think Cobol and file-based storage), each type with a variety
of
> applications and support needs.  We are in the running for getting a large
> contract from them and need to address their question:  "What makes
> PostgreSQL no more risky than any other database?"
> 
> Thanks in advance for your input.
> 
> Andy Yoder

Postgres, like the other database products out there, attempts to adhere to
an independent standard (SQL) as well as provide additional functionality
deemed useful but that falls outside the standard.  Its long existence and
usage in many different businesses and situations, as well as it regular
major-release schedule, shows that it is indeed "mainstream".  Even in a
worse-case scenario, were all new development to stop, prior stable releases
are available and proven in the market and already released under and
open-source license that cannot be revoked - unlike other licenses in the
market.

Aside from all that I would politely ask the client's IT group for specific
and detailed concerns that can be addressed with facts and not via simple
assertions that it works for other people.

If the client's IT group is going to be supporting the database then
"mainstream" has a different meaning than if all database management is
going to done by you and they are worried that PostgreSQL is insecure (which
is not just a function of the database but your entire infrastructure) or is
going to be too slow for the amount of data they are going to be accessing.
Specifics...

David J.





-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux