<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>postgresql Archives - ServerStadium</title>
	<atom:link href="https://serverstadium.com/knowledge-base/tag/postgresql/feed/" rel="self" type="application/rss+xml" />
	<link>https://serverstadium.com/knowledge-base/tag/postgresql/</link>
	<description>Public Cloud Solution by ServerStadium</description>
	<lastBuildDate>Fri, 24 May 2024 19:49:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://serverstadium.com/wp-content/uploads/2023/04/cropped-favicon-1-32x32.png</url>
	<title>postgresql Archives - ServerStadium</title>
	<link>https://serverstadium.com/knowledge-base/tag/postgresql/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Setting Up PostgreSQL with Docker on Server Stadium Cloud VMs or Dedicated Servers</title>
		<link>https://serverstadium.com/knowledge-base/setting-up-postgresql-with-docker-on-server-stadium/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Fri, 24 May 2024 19:49:37 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=11953</guid>

					<description><![CDATA[<p>Introduction PostgreSQL is a powerful, open-source object-relational database system known for its robustness, scalability, and performance. Using Docker to deploy PostgreSQL can simplify the setup and maintenance of your database environment. This guide will walk you through setting up a PostgreSQL database using Docker on Server Stadium infrastructure. Prerequisites Access to a Server Stadium cloud&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/setting-up-postgresql-with-docker-on-server-stadium/">Setting Up PostgreSQL with Docker on Server Stadium Cloud VMs or Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h3>Introduction</h3>
<p>PostgreSQL is a powerful, open-source object-relational database system known for its robustness, scalability, and performance. Using Docker to deploy PostgreSQL can simplify the setup and maintenance of your database environment. This guide will walk you through setting up a PostgreSQL database using Docker on Server Stadium infrastructure.</p>
<h3>Prerequisites</h3>
<ul>
<li>Access to a Server Stadium <a href="https://serverstadium.com/pricing/" target="_new" rel="noreferrer noopener">cloud VM</a> or <a href="https://serverstadium.com/dedicated-server/" target="_new" rel="noreferrer noopener">dedicated server</a> with Docker installed. If you need to install Docker, <a href="https://cp.serverstadium.com/regist-user" target="_new" rel="noreferrer noopener">sign up here</a> and refer to the official Docker page for installation instructions.</li>
<li>At least 2GB of RAM on your server for optimal performance.</li>
<li>Administrative or sudo privileges on your server.</li>
</ul>
<h3>Step 1: Pull the PostgreSQL Docker Image</h3>
<ol>
<li><strong>Download the PostgreSQL Image</strong><br />
Pull the latest PostgreSQL image from the Docker Hub: <div class="shortcode-code">
<p> docker pull postgres<br />
</p></div></li>
</ol>
<h3>Step 2: Run PostgreSQL in a Docker Container</h3>
<ol>
<li><strong>Start the PostgreSQL Container</strong><br />
Run a PostgreSQL container with a specified username, password, and database name: <div class="shortcode-code">
<p> docker run &#8211;name mypostgres -e POSTGRES_USER=myuser -e POSTGRES_PASSWORD=mypass -e POSTGRES_DB=mydb -p 5432:5432 -d postgres<br />
</p></div> This command sets environment variables for the user, password, and database, and maps port 5432 on the host to port 5432 in the container.</li>
</ol>
<h3>Step 3: Configure Persistent Data Storage</h3>
<ol>
<li><strong>Create a Docker Volume</strong><br />
To ensure data persistence across container restarts, create a Docker volume: <div class="shortcode-code">
<p> docker volume create pgdata<br />
</p></div></li>
<li><strong>Attach the Volume to the PostgreSQL Container</strong><br />
Start the PostgreSQL container with the volume attached: <div class="shortcode-code">
<p> docker run &#8211;name mypostgres -e POSTGRES_USER=myuser -e POSTGRES_PASSWORD=mypass -e POSTGRES_DB=mydb -p 5432:5432 -v pgdata:/var/lib/postgresql/data -d postgres<br />
</p></div></li>
</ol>
<h3>Step 4: Access and Manage the PostgreSQL Database</h3>
<ol>
<li><strong>Connect to the PostgreSQL Database</strong><br />
Connect to your PostgreSQL database using <code>psql</code> or any database management tool: <div class="shortcode-code">
<p> psql -h localhost -p 5432 -U myuser -d mydb<br />
</p></div> You will be prompted to enter the password specified earlier.</li>
</ol>
<h3>Step 5: Backup and Restore</h3>
<ol>
<li><strong>Backup the PostgreSQL Database</strong><br />
Backup your database using the <code>pg_dump</code> tool: <div class="shortcode-code">
<p> docker exec mypostgres pg_dump -U myuser mydb &gt; mydb_backup.sql<br />
</p></div></li>
<li><strong>Restore the PostgreSQL Database</strong><br />
Restore your database using <code>psql</code>: <div class="shortcode-code">
<p> cat mydb_backup.sql | docker exec -i mypostgres psql -U myuser -d mydb<br />
</p></div></li>
</ol>
<h3>Conclusion</h3>
<p>You have successfully set up a PostgreSQL database using Docker on your Server Stadium cloud VM or dedicated server. This setup not only ensures your data is managed efficiently but also leverages Docker for ease of deployment and scalability.</p>
<p>For more information on managing your PostgreSQL installation or other Docker-based applications, visit our <a href="https://serverstadium.com/knowledge-base/" target="_new" rel="noreferrer noopener">knowledge base</a> or consult the <a href="https://serverstadium.com/" target="_new" rel="noreferrer noopener">Server Stadium website</a>.</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/setting-up-postgresql-with-docker-on-server-stadium/">Setting Up PostgreSQL with Docker on Server Stadium Cloud VMs or Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Database Optimization on ServerStadium Servers</title>
		<link>https://serverstadium.com/knowledge-base/database-optimization-on-serverstadium-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Thu, 04 Jan 2024 04:16:18 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=11787</guid>

					<description><![CDATA[<p>Introduction Optimizing database performance is key to maintaining fast and reliable data access, especially in high-demand environments. On ServerStadium servers, fine-tuning your database, whether it&#8217;s MySQL, PostgreSQL, or MongoDB, can lead to significantly improved performance. This guide offers tips and best practices for optimizing these popular database systems on ServerStadium&#8217;s infrastructure. Database Optimization on ServerStadium&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/database-optimization-on-serverstadium-servers/">Database Optimization on ServerStadium Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Introduction</h2>
<p>Optimizing database performance is key to maintaining fast and reliable data access, especially in high-demand environments. On <a href="http://Https://ServerStadium">ServerStadium</a> servers, fine-tuning your database, whether it&#8217;s MySQL, PostgreSQL, or MongoDB, can lead to significantly improved performance. This guide offers tips and best practices for optimizing these popular database systems on ServerStadium&#8217;s infrastructure.</p>
<h2>Database Optimization on ServerStadium</h2>
<h3>Prerequisites</h3>
<ul>
<li>A ServerStadium VM or dedicated server (<a href="https://serverstadium.com/pricing/" target="_new" rel="noopener">VM Pricing</a>, <a href="https://serverstadium.com/dedicated-server/" target="_new" rel="noopener">Dedicated Servers</a>).</li>
<li>Basic knowledge of Linux and command-line interface.</li>
</ul>
<h3>General Optimization Tips</h3>
<p>Before diving into specific databases, here are some general optimization strategies:</p>
<ol>
<li><strong>Regular Maintenance</strong>: Regularly update and maintain your database software to the latest stable version.</li>
<li><strong>Monitor Performance</strong>: Utilize monitoring tools to track database performance and identify bottlenecks.</li>
<li><strong>Backup and Disaster Recovery</strong>: Regularly backup your databases and have a disaster recovery plan in place.</li>
</ol>
<h3>Optimizing MySQL on ServerStadium</h3>
<ol>
<li><strong>Tune Key Parameters</strong>: Adjust key settings in <code>my.cnf</code> like <code>innodb_buffer_pool_size</code>, <code>max_connections</code>, and <code>query_cache_size</code> based on your server&#8217;s resources and workload.</li>
<li><strong>Indexing</strong>: Properly index your tables to speed up query execution.</li>
<li><strong>Use EXPLAIN</strong>: Regularly use the <code>EXPLAIN</code> statement to analyze and optimize your SQL queries.</li>
<li><strong>Partitioning</strong>: Consider partitioning large tables to improve performance and management.</li>
</ol>
<h3>Optimizing PostgreSQL on ServerStadium</h3>
<ol>
<li><strong>Configuration Tuning</strong>: In <code>postgresql.conf</code>, tune parameters like <code>shared_buffers</code>, <code>work_mem</code>, <code>maintenance_work_mem</code>, and <code>effective_cache_size</code>.</li>
<li><strong>Vacuum and Analyze</strong>: Regularly run the <code>VACUUM</code> and <code>ANALYZE</code> commands to maintain database health.</li>
<li><strong>Index Maintenance</strong>: Use appropriate indexing strategies (B-tree, hash, GIN, etc.) for your queries and regularly monitor their performance.</li>
<li><strong>Connection Pooling</strong>: Use connection pooling to manage a large number of client connections efficiently.</li>
</ol>
<h3>Optimizing MongoDB on ServerStadium</h3>
<ol>
<li><strong>Sharding</strong>: Implement sharding to distribute data across multiple machines.</li>
<li><strong>Indexing</strong>: Proper indexing is crucial in MongoDB for query performance. Regularly review and optimize your indexes.</li>
<li><strong>Replication</strong>: Set up replication for data redundancy and high availability.</li>
<li><strong>Resource Allocation</strong>: Ensure that MongoDB has sufficient RAM and is configured to effectively use the available memory.</li>
</ol>
<h3>Conclusion</h3>
<p>Optimizing your database on ServerStadium servers can lead to significant performance improvements. By following these tips and regularly monitoring your database, you can ensure efficient, fast, and reliable data access.</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/database-optimization-on-serverstadium-servers/">Database Optimization on ServerStadium Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Configuring a PostgreSQL Database Cluster with Replication on ServerStadium</title>
		<link>https://serverstadium.com/knowledge-base/configuring-a-postgresql-database-cluster-with-replication-on-serverstadium/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Thu, 04 Jan 2024 02:11:32 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=11758</guid>

					<description><![CDATA[<p>This tutorial explains how to set up a PostgreSQL database cluster with replication using ServerStadium&#8217;s infrastructure. Prerequisites At least two ServerStadium VM instances or dedicated servers. Check ServerStadium VM Pricing and Dedicated Servers for options. Access to the ServerStadium Cloud Panel. Basic knowledge of PostgreSQL and Linux system administration. Step 1: Setting Up the Primary&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/configuring-a-postgresql-database-cluster-with-replication-on-serverstadium/">Configuring a PostgreSQL Database Cluster with Replication on ServerStadium</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>This tutorial explains how to set up a PostgreSQL database cluster with replication using ServerStadium&#8217;s infrastructure.</p>
<h3>Prerequisites</h3>
<ul>
<li>At least two ServerStadium VM instances or dedicated servers. Check <a href="https://serverstadium.com/pricing/" target="_new" rel="noopener">ServerStadium VM Pricing</a> and <a href="https://serverstadium.com/dedicated-server/" target="_new" rel="noopener">Dedicated Servers</a> for options.</li>
<li>Access to the <a href="https://cp.serverstadium.com/" target="_new" rel="noopener">ServerStadium Cloud Panel</a>.</li>
<li>Basic knowledge of PostgreSQL and Linux system administration.</li>
</ul>
<h3>Step 1: Setting Up the Primary PostgreSQL Server</h3>
<ol>
<li><strong>Select and Set Up Your Servers</strong>: Use the <a href="https://cp.serverstadium.com/" target="_new" rel="noopener">ServerStadium Cloud Panel</a> to set up at least two servers &#8211; one for the primary PostgreSQL server and the other for the replica.</li>
<li><strong>Install PostgreSQL</strong>: SSH into your primary server and install PostgreSQL:<br />
<div class="shortcode-code">
<p>sudo apt update<br />
sudo apt install postgresql postgresql-contrib</p></div></li>
<li><strong>Configure PostgreSQL for Replication</strong>:
<p>Edit the PostgreSQL configuration file:<br />
<div class="shortcode-code">
<p>sudo nano /etc/postgresql/12/main/postgresql.conf</p></div></p>
<p>Make the following changes (note that the version number, here <code>12</code>, may vary):</p>
<p>-Set the listen_addresses to &#8216;*&#8217; or the specific IP addresses of your replica servers.<br />
-Set the wal_level to replica.<br />
-Configure max_wal_senders to a number greater than or equal to the number of replicas you plan to have.<br />
-Set wal_keep_segments to a value that determines how much information to retain for the replicas (e.g., 64).</li>
<li><strong>Configure Client Authentication</strong>:
<p>Edit the <code>pg_hba.conf</code> file:<br />
<div class="shortcode-code">
<p>sudo nano /etc/postgresql/12/main/pg_hba.conf</p></div><br />
Add the following line to allow replication connections from your replicas (replace <code>replica_ip</code> with your replica&#8217;s IP):<br />
<div class="shortcode-code">
<p>host replication all replica_ip md5</p></div></li>
<li><strong>Restart PostgreSQL</strong>:<br />
<div class="shortcode-code">
<p>sudo systemctl restart postgresql</p></div></li>
</ol>
<h3>Step 2: Setting Up the Replica PostgreSQL Server</h3>
<ol>
<li><strong>Install PostgreSQL</strong>: Repeat the installation process on the replica server.</li>
<li><strong>Data Copy</strong>: On the primary server, create a user for replication and grant replication privileges. Then use <code>pg_basebackup</code> to copy data from the primary to the replica.
<p>On the primary server:<br />
<div class="shortcode-code">
<p>sudo -u postgres createuser &#8211;replication replica_user</p></div><br />
On the replica server:<br />
<div class="shortcode-code">
<p>sudo systemctl stop postgresql<br />
sudo -u postgres pg_basebackup -h primary_ip -D /var/lib/postgresql/12/main -U replica_user -P &#8211;wal-method=stream</p></div><br />
Replace <code>primary_ip</code> with the IP of your primary server.</li>
<li><strong>Configure Replica PostgreSQL</strong>:
<p>On the replica, create a recovery file:<br />
<div class="shortcode-code">
<p>sudo -u postgres nano /var/lib/postgresql/12/main/recovery.conf</p></div><br />
Add the following configuration:<br />
<div class="shortcode-code">
<p>standby_mode = &#039;on&#039;<br />
primary_conninfo = &#039;host=primary_ip port=5432 user=replica_user password=replica_password&#039;<br />
trigger_file = &#039;/tmp/postgresql.trigger.5432&#039;</p></div><br />
Replace <code>primary_ip</code> and <code>replica_password</code> with appropriate values.</li>
<li><strong>Start the Replica Server</strong>:<br />
<div class="shortcode-code">
<p>sudo systemctl start postgresql</p></div></li>
</ol>
<h3>Step 3: Testing and Verification</h3>
<ol>
<li><strong>Testing</strong>: Create a test database or table on the primary server. Verify that changes are replicated to the replica server.</li>
<li><strong>Monitoring</strong>: Use PostgreSQL’s built-in functions or external tools to monitor the replication status. Check logs for any errors.</li>
</ol>
<h3>Conclusion</h3>
<p>You now have a PostgreSQL database cluster with replication set up using ServerStadium&#8217;s services. This configuration enhances your database&#8217;s availability and load distribution.</p>
<p>For further assistance, refer to our <a href="https://serverstadium.com/knowledge-base/" target="_new" rel="noopener">knowledge base</a> or reach out to our support team.</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/configuring-a-postgresql-database-cluster-with-replication-on-serverstadium/">Configuring a PostgreSQL Database Cluster with Replication on ServerStadium</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Setting Up a PostgreSQL Database on ServerStadium&#8217;s Cloud Instances</title>
		<link>https://serverstadium.com/knowledge-base/setting-up-a-postgresql-database-on-serverstadiums-cloud-instances/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Fri, 26 May 2023 02:25:13 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=11662</guid>

					<description><![CDATA[<p>PostgreSQL is a powerful, open-source relational database system. This tutorial will guide you through setting up a PostgreSQL database on your ServerStadium cloud instance. Explore our Knowledge Base for more tutorials and guides. Step 1: Register Your Account If you haven&#8217;t done so already, register an account on our Registration Page. After filling out your&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/setting-up-a-postgresql-database-on-serverstadiums-cloud-instances/">Setting Up a PostgreSQL Database on ServerStadium&#8217;s Cloud Instances</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>PostgreSQL is a powerful, open-source relational database system. This tutorial will guide you through setting up a PostgreSQL database on your <strong>ServerStadium</strong> cloud instance.</p>
<p>Explore our <a href="https://serverstadium.com/knowledge-base/" target="_new" rel="noopener">Knowledge Base</a> for more tutorials and guides.</p>
<h2>Step 1: Register Your Account</h2>
<p>If you haven&#8217;t done so already, register an account on our <a href="https://cp.serverstadium.com/regist-user" target="_new" rel="noopener">Registration Page</a>. After filling out your details and creating your account, you&#8217;ll gain access to your personal <a href="https://cp.serverstadium.com/" target="_new" rel="noopener">Cloud Dashboard</a>.</p>
<h2>Step 2: Add Your Cloud Instance</h2>
<p>From your <a href="https://cp.serverstadium.com/" target="_new" rel="noopener">Cloud Dashboard</a>, click on the &#8216;Add VM&#8217; button. Here, you&#8217;ll find a range of cloud instance options. Select the one that suits your needs and budget. If you need help deciding, refer to our <a href="https://serverstadium.com/pricing/" target="_new" rel="noopener">Pricing Page</a> for more information.</p>
<h2>Step 3: Install PostgreSQL</h2>
<p>With your cloud instance ready, it&#8217;s time to install PostgreSQL. Connect to your instance via SSH and run the following commands:</p>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">sudo apt update</code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">sudo apt install postgresql postgresql-contrib</code></div>
<div>
<p>This will install PostgreSQL on your cloud instance. To verify the installation, type <code>psql --version</code>. You should see the version of PostgreSQL that&#8217;s been installed.</p>
<h2>Step 4: Create Your PostgreSQL Database</h2>
<p>Now that PostgreSQL is installed, you can create your database. To do this, you&#8217;ll need to switch to the PostgreSQL account on your instance:</p>
<div class="bg-black rounded-md mb-4">
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">sudo -i -u postgres<br />
</code></div>
</div>
<p>You can then access a PostgreSQL prompt using the <code>psql</code> command. From this prompt, you can create a database using the <code>CREATE DATABASE</code> command, like so:</p>
<div class="bg-black rounded-md mb-4">
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">CREATE DATABASE mydatabase;<br />
</code></div>
</div>
<p>Replace &#8220;mydatabase&#8221; with the name of your database.</p>
<h2>Conclusion</h2>
<p>Congratulations! You now have a PostgreSQL database set up on your ServerStadium cloud instance. You&#8217;re ready to start managing your data and leveraging the powerful features of ServerStadium&#8217;s cloud instances.</p>
<p>Our <a href="https://serverstadium.com/knowledge-base/" target="_new" rel="noopener">Knowledge Base</a> is filled with other tutorials, guides, and tips. If you need any assistance, don&#8217;t hesitate to contact our support team.</p>
</div>
<p>The post <a href="https://serverstadium.com/knowledge-base/setting-up-a-postgresql-database-on-serverstadiums-cloud-instances/">Setting Up a PostgreSQL Database on ServerStadium&#8217;s Cloud Instances</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Set Up High Availability PostgreSQL Cluster Using Patroni on ServerStadium</title>
		<link>https://serverstadium.com/knowledge-base/set-up-high-availability-postgresql-cluster-using-patroni-on-serverstadium/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Wed, 06 Jul 2022 07:40:20 +0000</pubDate>
				<guid isPermaLink="false">https://cloudraya.com/knowledge-base/?p=2096</guid>

					<description><![CDATA[<p>PostgreSQL is a powerful OpenSource, an object-relational database management system that extends the SQL language with many features. Meanwhile, Patroni is an OpenSource python package that we can use to manage and automate the deployment of PostgreSQL HA Clusters. Little information, Patroni was developed by Zalando. Prerequisite To follow this tutorial, we need three VM&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/set-up-high-availability-postgresql-cluster-using-patroni-on-serverstadium/">Set Up High Availability PostgreSQL Cluster Using Patroni on ServerStadium</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">PostgreSQL is a powerful OpenSource, an object-relational database management system that extends the SQL language with many features.</p>



<p class="wp-block-paragraph">Meanwhile, Patroni is an OpenSource python package that we can use to manage and automate the deployment of PostgreSQL HA Clusters. Little information, Patroni was developed by Zalando.</p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Prerequisite</strong></h2>



<p class="wp-block-paragraph">To follow this tutorial, we need three VM for PostgreSQL and one VM for HAproxy and etcd.<br>Below is four VMs that we will deploy in ServerStadium.</p>



<div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-8f761849 wp-block-columns-is-layout-flex">
<div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:100%">
<figure class="wp-block-table"><table><tbody><tr><td class="has-text-align-center" data-align="center"><strong>Hostname</strong></td><td class="has-text-align-center" data-align="center"><strong>IP Address</strong></td><td class="has-text-align-left" data-align="left"><strong>Applications</strong></td></tr><tr><td class="has-text-align-center" data-align="center">haetcd</td><td class="has-text-align-center" data-align="center">199.180.130.99</td><td class="has-text-align-left" data-align="left">HAproxy</td></tr><tr><td class="has-text-align-center" data-align="center"></td><td class="has-text-align-center" data-align="center">10.3.3.166</td><td class="has-text-align-left" data-align="left">etcd</td></tr><tr><td class="has-text-align-center" data-align="center">pgsql1</td><td class="has-text-align-center" data-align="center">10.3.3.12</td><td class="has-text-align-left" data-align="left">patroni</td></tr><tr><td class="has-text-align-center" data-align="center">pgsql2</td><td class="has-text-align-center" data-align="center">10.3.3.71</td><td class="has-text-align-left" data-align="left">patroni</td></tr><tr><td class="has-text-align-center" data-align="center">pgsql3</td><td class="has-text-align-center" data-align="center">10.3.3.70</td><td class="has-text-align-left" data-align="left">patroni</td></tr></tbody></table></figure>
</div>
</div>



<p class="wp-block-paragraph">We will use haetcd as jumpbox server since the VM has Public IP Address that we can access from the outside network. In /etc/host, insert the hostname of the servers to make us easy to access the server without remembering the IP Address.</p>



<p class="wp-block-paragraph">/etc/hosts</p>



<figure class="wp-block-image size-full"><img decoding="async" width="284" height="144" src="https://serverstadium.com/wp-content/uploads/2022/05/image.png" alt="" class="wp-image-2098"/></figure>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Install PostgreSQL 14</strong></h2>



<p class="wp-block-paragraph">In this step, we will use PostgreSQL14 for pgsql1, pgsql2, and pgsql3. Please the command below on each server.</p>



<pre class="wp-block-preformatted"><code>sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" &gt; /etc/apt/sources.list.d/pgdg.list'</code>
<code>
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -

apt update</code></pre>



<figure class="wp-block-image size-full"><img fetchpriority="high" decoding="async" width="1157" height="260" src="https://serverstadium.com/wp-content/uploads/2022/05/image-2.png" alt="" class="wp-image-2100" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-2.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-2-300x67.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-2-1024x230.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-2-768x173.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<pre class="wp-block-preformatted">apt -y install postgresql-14 postgresql-server-dev-14</pre>



<figure class="wp-block-image size-full"><img decoding="async" width="1157" height="131" src="https://serverstadium.com/wp-content/uploads/2022/05/image-3.png" alt="" class="wp-image-2101" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-3.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-3-300x34.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-3-1024x116.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-3-768x87.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph">After the postgresql installation is completed, we need to stop and disable PostgreSQL service. Then we will continue to install patroni.</p>



<p class="wp-block-paragraph"> <code>systemctl stop postgresql &amp;&amp; systemctl disable postgresql</code></p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Install Patroni</strong></h2>



<p class="wp-block-paragraph">Patroni uses the utilities of PostgreSQL that we have installed previously which is located at <strong>/usr/lib/postgresql/versin/bin </strong>directory.</p>



<p class="wp-block-paragraph">In this step, we create a symbolic link to PostgreSQL utilities on psql1, psql2, and psql3 </p>



<p class="wp-block-paragraph"><code>ln -s /usr/lib/postgresql/14/bin/* /usr/sbin/ </code></p>



<p class="wp-block-paragraph">Next, we will install patroni on each server</p>



<p class="wp-block-paragraph"><code>apt -y install python3 python3-pip <br>pip install --upgrade setuptools <br>pip install psycopg2 <br>pip install patroni <br>pip install python-etcd</code></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="340" src="https://serverstadium.com/wp-content/uploads/2022/05/image-4.png" alt="" class="wp-image-2102" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-4.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-4-300x88.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-4-1024x301.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-4-768x226.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph"></p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Configure Patroni on Pgsql1, Pgsql2, and Pgsql3</strong></h2>



<p class="wp-block-paragraph">Patroni uses yaml files to store the configuration. We will place the yaml file on /etc directory. </p>



<pre class="wp-block-preformatted">sudo nano /etc/patroni.yml

<strong>pgsql1:</strong>
scope: postgres
namespace: /db/
name: <strong>pgsql1</strong>

restapi:
    listen: <strong>10.3.3.12</strong>:8008
    connect_address: <strong>10.3.3.12</strong>:8008

etcd:
    host:  <strong>10.3.3.166</strong>:2379

bootstrap:
    dcs:
        ttl: 30
        loop_wait: 10
        retry_timeout: 10
        maximum_lag_on_failover: 1048576
        postgresql:
            use_pg_rewind: true

    initdb:
    - encoding: UTF8
    - data-checksums

    pg_hba:
    - host replication replicator 127.0.0.1/32 md5
    - host replication replicator 10.3.3.12/0 md5
    - host replication replicator 10.3.3.71/0 md5
    - host replication replicator 10.3.3.70/0 md5
    - host all all 0.0.0.0/0 md5

    users:
        admin:
            password: admin
            options:
                - createrole
                - createdb

postgresql:
    listen: <strong>10.3.3.12</strong>:5432
    connect_address: <strong>10.3.3.12</strong>:5432
    data_dir: /data/patroni
    pgpass: /tmp/pgpass
    authentication:
        replication:
            username: replicator
            password: replogin321
        superuser:
            username: postgres
            password: secretlogin321
    parameters:
        unix_socket_directories: '.'

tags:
    nofailover: false
    noloadbalance: false
    clonefrom: false
    nosync: false

<strong>pgsql2</strong>
scope: postgres
namespace: /db/
name: <strong>pgsql2</strong>

restapi:
    listen: <strong>10.3.3.71</strong>:8008
    connect_address: <strong>10.3.3.71</strong>:8008

etcd:
    host:  <strong>10.3.3.166</strong>:2379

bootstrap:
    dcs:
        ttl: 30
        loop_wait: 10
        retry_timeout: 10
        maximum_lag_on_failover: 1048576
        postgresql:
            use_pg_rewind: true

    initdb:
    - encoding: UTF8
    - data-checksums

    pg_hba:
    - host replication replicator 127.0.0.1/32 md5
    - host replication replicator 10.3.3.12/0 md5
    - host replication replicator 10.3.3.71/0 md5
    - host replication replicator 10.3.3.70/0 md5
    - host all all 0.0.0.0/0 md5

    users:
        admin:
            password: admin
            options:
                - createrole
                - createdb

postgresql:
    listen: <strong>10.3.3.71</strong>:5432
    connect_address: <strong>10.3.3.71</strong>:5432
    data_dir: /data/patroni
    pgpass: /tmp/pgpass
    authentication:
        replication:
            username: replicator
            password: replogin321
        superuser:
            username: postgres
            password: secretlogin321
    parameters:
        unix_socket_directories: '.'

tags:
    nofailover: false
    noloadbalance: false
    clonefrom: false
    nosync: false

<strong>pgsql3
</strong>scope: postgres
namespace: /db/
name: <strong>pgsql3</strong>

restapi:
    listen: <strong>10.3.3.70</strong>:8008
    connect_address: <strong>10.3.3.70</strong>:8008

etcd:
    host:  10.3.3.166:2379

bootstrap:
    dcs:
        ttl: 30
        loop_wait: 10
        retry_timeout: 10
        maximum_lag_on_failover: 1048576
        postgresql:
            use_pg_rewind: true

    initdb:
    - encoding: UTF8
    - data-checksums

    pg_hba:
    - host replication replicator 127.0.0.1/32 md5
    - host replication replicator 10.3.3.12/0 md5
    - host replication replicator 10.3.3.71/0 md5
    - host replication replicator 10.3.3.70/0 md5
    - host all all 0.0.0.0/0 md5

    users:
        admin:
            password: admin
            options:
                - createrole
                - createdb

postgresql:
    listen: <strong>10.3.3.70</strong>:5432
    connect_address: <strong>10.3.3.70</strong>:5432
    data_dir: /data/patroni
    pgpass: /tmp/pgpass
    authentication:
        replication:
            username: replicator
            password: replogin321
        superuser:
            username: postgres
            password: secretlogin321
    parameters:
        unix_socket_directories: '.'

tags:
    nofailover: false
    noloadbalance: false
    clonefrom: false
    nosync: false
</pre>



<p class="wp-block-paragraph">According to the yml file, the data of PostgreSQL will be stored at /data/patroni. Make sure the ownership of that directory is postgres.</p>



<p class="wp-block-paragraph"><code>mkdir -p /data/patroni</code><br>chown postgres:postgres /data/patroni<br><code>chmod 700 /data/patroni</code></p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Create a Service</strong></h2>



<p class="wp-block-paragraph">Next, we will create patroni service that allow us to start and stop the service on each server.</p>



<p class="wp-block-paragraph"><code>sudo nano /etc/systemd/system/patroni.service</code></p>



<p class="wp-block-paragraph">Add the following parameter in the patroni.service<code><br>[Unit]<br>Description=High availability PostgreSQL Cluster<br>After=syslog.target network.target<br>[Service]<br>Type=simple<br>User=postgres<br>Group=postgres<br>ExecStart=/usr/local/bin/patroni /etc/patroni.yml<br>KillMode=process<br>TimeoutSec=30<br>Restart=no<br><br>[Install]<br>WantedBy=multi-user.target</code></p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Create and Enable Patroni Service</strong></h2>



<p class="wp-block-paragraph">After the patroni service has been created then we enable it to make it autostart.</p>



<p class="wp-block-paragraph"><code>sudo systemctl daemon-reload<br>sudo systemctl enable patroni</code></p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Install Etcd and Haproxy</strong> <strong>on Haetcd VM</strong></h2>



<p class="wp-block-paragraph">etcd is a fault-tolerant, a distributed key value store that can be used to store the state of PostgreSQL cluster.  With etcd, it will keep the PostgreSQL cluster up and running.</p>



<p class="wp-block-paragraph">Run the command below to install etcd</p>



<pre class="wp-block-preformatted">sudo apt -y install etcd</pre>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="156" src="https://serverstadium.com/wp-content/uploads/2022/05/image-5.png" alt="" class="wp-image-2104" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-5.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-5-300x40.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-5-1024x138.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-5-768x104.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph">Next step, we will configure the etcd file. Add the below parameter in the etcd file:</p>



<p class="wp-block-paragraph"><code>sudo nano /etc/default/etcd</code></p>



<p class="wp-block-paragraph"><code>ETCD_LISTEN_PEER_URLS="http://<strong>10.3.3.166</strong>:2380"<br>ETCD_LISTEN_CLIENT_URLS="http://localhost:2379,http://<strong>10.3.3.166</strong>:2379"<br>ETCD_INITIAL_ADVERTISE_PEER_URLS="http://<strong>10.3.3.166</strong>:2380"<br>ETCD_INITIAL_CLUSTER="default=http://<strong>10.3.3.166</strong>:2380"<br>ETCD_ADVERTISE_CLIENT_URLS="http://<strong>10.3.3.166</strong>:2379"<br>ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"<br>ETCD_INITIAL_CLUSTER_STATE="new"</code><br></p>



<p class="wp-block-paragraph">Restart the etcd service to make a change effect</p>



<p class="wp-block-paragraph"><code>sudo systemctl restart etcd<br></code></p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Start Patroni on Each Pgsql Server</strong></h2>



<p class="wp-block-paragraph">Before we start the patroni service, we need to activate the watchdog support to prevent split-brain on the PostgreSQL<br><br>https://patroni.readthedocs.io/en/latest/watchdog.html<br><br><code>modprobe softdog<br>chown postgres /dev/watchdog</code></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="705" height="56" src="https://serverstadium.com/wp-content/uploads/2022/05/image-6.png" alt="" class="wp-image-2105" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-6.png 705w, https://serverstadium.com/wp-content/uploads/2022/05/image-6-300x24.png 300w" sizes="(max-width: 705px) 100vw, 705px" /></figure>



<p class="wp-block-paragraph">After the watchdog is activated, now we can start the patroni service again on each server.</p>



<p class="wp-block-paragraph"><code>systemctl start patroni</code><br><code>systemctl status patroni</code></p>



<p class="wp-block-paragraph">pgsql1 as master. <br>We can see, the pgsql1 will act as the PostgreSQL master</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="372" src="https://serverstadium.com/wp-content/uploads/2022/05/image-7.png" alt="" class="wp-image-2106" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-7.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-7-300x96.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-7-1024x329.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-7-768x247.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph">pgsql2 and pgsql3 as slave</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="366" src="https://serverstadium.com/wp-content/uploads/2022/05/image-8.png" alt="" class="wp-image-2107" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-8.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-8-300x95.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-8-1024x324.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-8-768x243.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="353" src="https://serverstadium.com/wp-content/uploads/2022/05/image-9.png" alt="" class="wp-image-2108" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-9.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-9-300x92.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-9-1024x312.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-9-768x234.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><strong>Install Haproxy</strong></h2>



<p class="wp-block-paragraph">Our last step install HAproxy service to give us an endpoint to which the application can connect to the database.</p>



<p class="wp-block-paragraph"><code>sudo apt -y install haproxy</code></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="146" src="https://serverstadium.com/wp-content/uploads/2022/05/image-10.png" alt="" class="wp-image-2109" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-10.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-10-300x38.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-10-1024x129.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-10-768x97.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph" id="block-afeeab82-1a19-4d69-a234-c7d500db5846">Edit the haproxy file configuration as follow</p>



<pre class="wp-block-preformatted"><code>nano /etc/haproxy/haproxy.cfg</code>
global
    maxconn 100

defaults
    log global
    mode tcp
    retries 2
    timeout client 30m
    timeout connect 4s
    timeout server 30m
    timeout check 5s

listen stats
    mode http
    bind *:7000
    stats enable
    stats uri /

listen postgres
    bind *:5000
    option httpchk
    http-check expect status 200
    default-server inter 3s fall 3 rise 2 on-marked-down shutdown-sessions
    server pgsql1 <strong>10.3.3.12</strong>:5432 maxconn 100 check port 8008
    server pgsql2 <strong>10.3.3.71</strong>:5432 maxconn 100 check port 8008
    server pgsql3 <strong>10.3.3.70</strong>:5432 maxconn 100 check port 8008
</pre>



<p class="wp-block-paragraph">Check our haproxy configuration using the following command:</p>



<pre class="wp-block-preformatted">sudo /usr/sbin/haproxy -c -V -f /etc/haproxy/haproxy.cfg&nbsp;</pre>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1000" height="54" src="https://serverstadium.com/wp-content/uploads/2022/05/image-11.png" alt="" class="wp-image-2110" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-11.png 1000w, https://serverstadium.com/wp-content/uploads/2022/05/image-11-300x16.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-11-768x41.png 768w" sizes="(max-width: 1000px) 100vw, 1000px" /></figure>



<p class="wp-block-paragraph">If the configuration is valid, we can restart our haproxy service</p>



<p class="wp-block-paragraph"><code>sudo systemctl restart haproxy</code></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="307" src="https://serverstadium.com/wp-content/uploads/2022/05/image-12.png" alt="" class="wp-image-2111" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-12.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-12-300x80.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-12-1024x272.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-12-768x204.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">In the final step, we can monitor the PostgreSQL cluster using the browser as shown in the screenshot below:</p>



<p class="wp-block-paragraph"><a href="http://199.180.130.99:7000/">http://199.180.130.99:7000/</a></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="380" src="https://serverstadium.com/wp-content/uploads/2022/05/image-13.png" alt="" class="wp-image-2112" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-13.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-13-300x99.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-13-1024x336.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-13-768x252.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph">As we can see, psql1 is the leader of the PostgreSQL cluster with the green line row.<br>Now we will kill patroni service on psql1, to see which VM will be acting as the leader.</p>



<p class="wp-block-paragraph"><code>systemctl stop patroni</code></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1157" height="374" src="https://serverstadium.com/wp-content/uploads/2022/05/image-14.png" alt="" class="wp-image-2113" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-14.png 1157w, https://serverstadium.com/wp-content/uploads/2022/05/image-14-300x97.png 300w, https://serverstadium.com/wp-content/uploads/2022/05/image-14-1024x331.png 1024w, https://serverstadium.com/wp-content/uploads/2022/05/image-14-768x248.png 768w" sizes="(max-width: 1157px) 100vw, 1157px" /></figure>



<p class="wp-block-paragraph">After we stop service patroni service in psql1, the psql2 will be elected as the leader node.</p>



<h2 class="has-vivid-cyan-blue-color has-text-color wp-block-heading"><br><strong>Test PostgresSQL Cluster</strong></h2>



<p class="wp-block-paragraph">If we want to make a connection to PostgreSQL, we use the IP Address of HAProxy and port 5000.</p>



<p class="wp-block-paragraph"><code>su - postgres<br>psql -U postgres -h 199.180.130.99 -p 5000</code></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="550" height="96" src="https://serverstadium.com/wp-content/uploads/2022/05/image-15.png" alt="" class="wp-image-2120" srcset="https://serverstadium.com/wp-content/uploads/2022/05/image-15.png 550w, https://serverstadium.com/wp-content/uploads/2022/05/image-15-300x52.png 300w" sizes="(max-width: 550px) 100vw, 550px" /></figure>



<p class="wp-block-paragraph"><br>You now have a high availability PostgreSQL Cluster in ServerStadium that is ready to use.<br>Please don&#8217;t hesitate to <a href="https://serverstadium.com/id/contact/" target="_blank" rel="noreferrer noopener">contact ServerStadium support</a> if you need further assistance.</p>



<p class="wp-block-paragraph">Find more tutorials articles about ServerStadium in our Knowledge Base, or if you want to get more general knowledge about technology feel free to visit our <a href="https://serverstadium.com/blog/" target="_blank" rel="noreferrer noopener">Blog.</a> </p>



<p class="wp-block-paragraph">Curious to know more about our products and panel? register <a href="https://cp.serverstadium.com/regist-user" target="_blank" rel="noreferrer noopener">here</a> for free!.</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/set-up-high-availability-postgresql-cluster-using-patroni-on-serverstadium/">Set Up High Availability PostgreSQL Cluster Using Patroni on ServerStadium</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
