<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High Availability on iSquiz.com</title><link>https://www.isquiz.com/tags/high-availability/</link><description>Recent content in High Availability on iSquiz.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>iSquiz.com</copyright><lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.isquiz.com/tags/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>Single-Server PostgreSQL: When a Business Needs a Standby</title><link>https://www.isquiz.com/post/single-server-database-high-availability/</link><pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.isquiz.com/post/single-server-database-high-availability/</guid><description>
&lt;p&gt;A small business keeps its orders, invoices and customer list in one &lt;a href="https://www.postgresql.org/docs/current/high-availability.html"&gt;PostgreSQL&lt;/a&gt; server. If that machine stops, nothing takes over. Moving to a managed host does not fix that by itself, because &lt;a href="https://docs.cloud.google.com/sql/docs/postgres/high-availability"&gt;Cloud SQL doesn't recover standalone instances from a zonal outage automatically&lt;/a&gt;. PostgreSQL's own &lt;a href="https://www.postgresql.org/docs/current/warm-standby.html"&gt;streaming replication is asynchronous by default&lt;/a&gt;, so a standby does not guarantee zero data loss either.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="what-a-single-database-server-puts-at-risk"&gt;What a single database server puts at risk&lt;/h2&gt;
&lt;p&gt;High availability means &lt;a href="https://www.postgresql.org/docs/current/high-availability.html"&gt;database servers working together so a second server can take over quickly if the primary fails&lt;/a&gt;. A standby that accepts no connections until it is promoted is a warm standby. One that accepts connections and serves read-only queries is a hot standby. In PostgreSQL 18 the &lt;a href="https://www.postgresql.org/docs/current/runtime-config-replication.html"&gt;&lt;code&gt;hot_standby&lt;/code&gt; setting is on by default&lt;/a&gt;, so a standby can answer queries while it replays changes from the primary.&lt;/p&gt;</description></item></channel></rss>