{"id":47172,"date":"2024-07-26T10:23:09","date_gmt":"2024-07-26T10:23:09","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=47172"},"modified":"2026-02-18T07:28:30","modified_gmt":"2026-02-18T07:28:30","slug":"psotgresql-auto-clustering","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/psotgresql-auto-clustering","title":{"rendered":"PostgreSQL Auto-Clustering"},"content":{"rendered":"

PostgreSQL Auto-Clustering<\/h2>\n

Data plays a crucial role in most applications and should remain accessible to end users in a dynamic environment. Storing all your data in one place is risky if the system fails.<\/p>\n

To ensure high availability,<\/strong> it is essential to implement a strategy that maintains data across multiple synchronized servers.<\/p>\n

Replicating your data across multiple databases helps mitigate system failures.
\nIt also boosts productivity, enables efficient backup processes, and allows for data analysis without degrading performance<\/p>\n

AccuWeb.Cloud provides PostgreSQL with master-slave asynchronous replication using certified templates among its range of database clustering solutions. By default, it deploys two database containers, one for each role\u2014Master and Slave.<\/strong><\/p>\n

The primary (master) server hosts an active instance of the database and handles read-write operations, while the standby (slave) server maintains a copy of the active database and manages read-only<\/strong> operations.<\/p>\n

If the primary database fails due to container issues or database corruption, the slave server (operating in a separate container) must be promoted to master to retain writes and ensure database availability.<\/p>\n

\"PostgreSQL<\/a><\/p>\n

In the cluster topology, each database container is configured with default vertical scaling,<\/a> ranging from 1 reserved cloudlet to 32 dynamic cloudlets (up to 4 GiB of RAM and 6.4 GHz of CPU)<\/strong>, which are allocated dynamically based on incoming load. You can adjust the resource allocation limit by following the linked guide.<\/p>\n

The Database Cluster can be installed automatically through the following methods:<\/strong><\/p>\n

    \n
  1. As a Marketplace application<\/a><\/li>\n
  2. Using the embedded Auto-Clustering feature in the Dashboard<\/a><\/li>\n<\/ol>\n

    In this tutorial, we will delve into both methods.<\/p>\n

    Installing a PostgreSQL Cluster from the Marketplace<\/h2>\n

    You can easily locate the PostgreSQL Master-Slave Cluster package in the Marketplace.<\/p>\n

    \"PostgreSQL<\/a><\/p>\n

    Modify the database version, environment name, and destination region as needed within the installation window.<\/p>\n

    PostgreSQL Automatic Clustering Mode<\/h2>\n

    In AccuWeb.Cloud, enabling auto-clustering is made simple with a dedicated switch designed to streamline the clustering process.<\/p>\n

    To activate it, access the topology wizard in the dashboard, select your software stack (e.g., PostgreSQL 15), and toggle the Auto-Clustering switch to the on position.<\/p>\n

    \"Automatic<\/a><\/p>\n

    Cluster Topology<\/h2>\n

    The database cluster topology resulting from both deployments is depicted as follows:<\/p>\n

    \"Cluster<\/a><\/p>\n

    Once the database cluster installation is finished, you will receive a confirmation message containing the master node URL and database access credentials. Additionally, this information will be sent to you via email for your records.<\/p>\n

    \"Cluster<\/a><\/p>\n

    Now, let’s activate the master database to verify the successful replication of data to the slave.<\/p>\n

    Testing PostgreSQL Database Replication Functionality<\/h2>\n

    To verify proper data replication, we will create a new database instance in the master container and confirm its presence in the slave.<\/p>\n

    Create a New Database<\/h3>\n

    Step 1.<\/strong> Click on “Open in Browser”<\/strong> next to the PostgreSQL Master node to access the phpPgAdmin<\/strong> web interface.<\/p>\n

    \"Open<\/a><\/p>\n

    Step 2.<\/strong> Navigate to Servers,<\/strong> select PostgreSQL,<\/strong> and log in using the credentials provided during cluster installation.<\/p>\n

    \"Login<\/a><\/p>\n

    Step 3<\/strong>. Select “Create database”<\/strong> from the menu.<\/p>\n

    \"Create<\/a><\/p>\n

    Step 4.<\/strong> Enter a name in the Name box<\/strong> (e.g., test) and click on the Create<\/strong> button.<\/p>\n

    \"Enter<\/a><\/p>\n

    Now that the database is created on the master node, let’s verify the replicated data on the slave node.<\/p>\n

    Check the Replication<\/h2>\n

    Step 1.<\/strong> Open the phpPgAdmin web interface by clicking on “Open in Browser”<\/strong> next to the PostgreSQL Slave node.<\/p>\n

    \"Check<\/a><\/p>\n

    Step 2.<\/strong> Log in to the admin interface using the same username and password that you used to access the master node<\/p>\n

    \"Access<\/a><\/p>\n

    Once logged in, you’ll find the replicated database (e.g., test) visible.<\/p>\n

    Congratulations! Your PostgreSQL environment with master-slave asynchronous replication is now operational and ready for data processing.<\/p>\n

    Next, connect this PostgreSQL replicated database to your project. Follow the instructions below based on your application specifics:<\/p>\n