A: There are several companies which provide paid support for PostgreSQL. Most of them are regional in nature. People should contact the nearest regional contact volunteer to be connected with one or more companies, or check our <a href="/support/professional_services">professional services list</a>.</p>
<p><b>Q: What's the relationship between the PostgreSQL Project, EnterpriseDB, 2ndQuadrant, CommandPrompt, SRA, Greenplum and others?</b><br />
-A: The PostgreSQL project enjoys the support of multiple companies who sell products or services built with PostgreSQL, and in turn contribute code, money and staff time to the project. None of them "own" PostgreSQL, nor is and individual company responsible for PostgreSQL code development. This is the same as Linux, Apache or FreeBSD.</p>
+A: The PostgreSQL project enjoys the support of multiple companies who sell products or services built with PostgreSQL, and in turn contribute code, money and staff time to the project. None of them "own" PostgreSQL, nor is any individual company responsible for PostgreSQL code development. This is the same as Linux, Apache and FreeBSD.</p>
<p><b>Q: How does PostgreSQL compare to MySQL?</b><br />
-A: This is a topic that can start several hours of discussion. As a quick summary, MySQL is the "easy-to-use, web developer" database, and PostgreSQL is the "feature-rich, standards-compliant" database. PostgreSQL is liberally licensed and owned by its community; MySQL is GPL-licensed and owned by Oracle. Beyond that, each database user should make their own evaluation; open source software makes doing your own comparison very easy.</p>
-
-<p><b>Q: Are users migrating from MySQL to PostgreSQL in the wake of the Oracle acquisition?</b><br />
-Some of them, yes. We have seen an increased number of requests for MySQL to PostgreSQL migration information in the last year. Some users are migrating to other database systems. However, the majority of MySQL users are likely continuing to use MySQL; it is still open source. A few users are also migrating from Sybase due to its aquisition.</p>
+A: This is a topic that can start several hours of discussion. As a quick summary, MySQL is the "easy-to-use, web developer" database, and PostgreSQL is the "feature-rich, standards-compliant" database. PostgreSQL is liberally licensed and owned by its community; MySQL is GPL-licensed and owned by Oracle. Beyond that, each database user should make his own evaluation; open source software makes doing comparisons very easy.</p>
<p><b>Q: How does PostgreSQL compare to Oracle/DB2/MS SQL Server/Informix?</b><br />
A: Our feature set is generally considered to be very competitive with other leading SQL RDBMSes. Certainly there are features some of them have which we don't, and the reverse is also true. To date, only a few benchmarks have been published showing PostgreSQL to be within 10-30% of proprietary competitors. However, we have had many users migrate from other database systems – primarily Oracle and Informix – and they are completely satisfied with the performance of their PostgreSQL systems.</p>
A: Currently, we have a shared history but no shared code with Ingres. Our developers have contact with the Ingres engineers, as we do with all open source database developers, but we have not done a direct comparison of the two DBMSes.</p>
<p><b>Q: Is 9.0's replication expected to be the only replication in the future?</b><br />
-A: No. While 9.0's binary replication is extremely popular, it does not fit all replication tasks. We expect Slony-I, Bucardo, pgPool2, Londiste and other tools to continue being widely used among users who have specific or advanced needs. For example, users who need to replicate only specific tables, users who need to replicate between PostgreSQL versions, or users who need to do offline multi-master replication.</p>
+A: No. While 9.0's binary replication is extremely popular, it does not fit all replication tasks. We expect Slony-I, Bucardo, pgPool2, Londiste and other tools to continue being widely used among users who have specific or advanced needs. Examples include replicating only specific tables, replicating between PostgreSQL different versions, or offline multi-master replication.</p>
<p><b>Q: When will PostgreSQL get database server clustering?</b><br />
A: We already have it. Since no one type of clustering satisfies all needs, we have several different clustering tools which take various clustering approaches. The open source projects PostgresXC, GridSQL, pgCluster, pgPool2, CyberCluster and Sequoia are available, as well as proprietary tools Greenplum Database, and Uni/Cluster. For more advanced clustering options, see Skype's Skytools or the experimental project Postgres-R. Also, PostgreSQL is supported by filesystem-based clustering systems for failover, including ones from Red Hat, Microsoft, Veritas and Oracle.</p>