Re: Justifying a PG over MySQL approach to a project
От | Greg Smith |
---|---|
Тема | Re: Justifying a PG over MySQL approach to a project |
Дата | |
Msg-id | 4B2F1781.5010202@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: Justifying a PG over MySQL approach to a project (Ron Mayer <rm_pg@cheapcomplexdevices.com>) |
Список | pgsql-general |
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@2ndQuadrant.com www.2ndQuadrant.com
В списке pgsql-general по дате отправления: