Deployment Limitations

The first BETA release of Tungsten Clustering for PostgreSQL has a small number of limitations. It is intended that these limitations will be removed in subsequent BETA updates and in the final GA release. If you have any queries, please contact Continuent Support through the usual channels.

• Only standalone clusters can be deployed at this time, consisting of 1 Primary and multiple replica nodes. Total number of nodes must be an odd number to maintain quorum. The minimum deployment is a 3-node cluster. Active Witness nodes are also supported, for example you can deploy a 3-node cluster consisting of 2 full database nodes and 1 Witness node. (See "Active Witness Hosts" for more information on Witness hosts).
• The cluster is deployed with a template configuration with properties that can be adjusted, however no additional advanced properties can be added at this time. This produces a configuration which is sufficient for testing and POC purposes. It is NOT recommended to use this BETA release in a production environment. More information can be found here: "Tungsten Properties"
• Only installations can be achieved in the first release, the ability to update will be included in subsequent releases.
• The installation is handled by Ansible, providing a much quicker and simpler deployment than the TPM methods used with Tungsten Clustering for MySQL.
• The connectors are deployed (and must remain) in Proxy mode. Bridge mode is not supported.
• Schema changes (DDL) must be executed through a proxy node to ensure replication to replica nodes.
• The Ansible deployment scripts expects the hosts to be clean machines and will deploy and configure PostgreSQL as part of the installation, meaning that installation against existing PostgreSQL databases is currently not supported
• The installation creates an initial default PostgreSQL database called testing, to change this, specify the pg_dbname option to the Ansible deployment command.