Ron Mayer wrote:
* There are enough large companies that depend entirely
on each of the databases that make either one a save
choice from that point of view (Skype). And the way
Apple and Cisco use it for a number of their programs
Yeah, these are all good examples. Cisco uses PostgreSQL in a number of
products:
Carrier-Sensitive Routing:
http://www.cisco.com/en/US/products/sw/voicesw/ps4371/products_user_guide_chapter09186a00800c252c.html
Fabric Manager:
http://www.cisco.com/en/.../product_data_sheet09186a00800c4656.pdf
That have non-trivial uptime requirements. "Call routing" is not a
field particularly tolerant of the "my database got corrupted and went
down" kind of errors.
You'll similarly find PostgreSQL used inside Japan's Nippon Telegraph
and Telephone Corporation (NTT) too, enough so that they're doing major
development to improve it (they're sponsoring the "Streaming
Replication" feature targeted for 8.5). When the telcos and providers
of telco equipment like Skype, Cisco, and NTT are all using PostgreSQL,
it certainly makes it easy to support the idea that the database is
reliable in the real world.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg@xxxxxxxxxxxxxxx www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
