<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>High-Availability on kylorend3r Blog</title><link>https://kylorend3r.github.io/tags/high-availability/</link><description>Recent content in High-Availability on kylorend3r Blog</description><image><title>kylorend3r Blog</title><url>https://kylorend3r.github.io/og-image.png</url><link>https://kylorend3r.github.io/og-image.png</link></image><generator>Hugo -- 0.146.0</generator><language>en-us</language><lastBuildDate>Sun, 05 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kylorend3r.github.io/tags/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>Same Cluster, Different Rules. synchronous_standby_names vs synchronized_standby_slots</title><link>https://kylorend3r.github.io/posts/synchronous-standby-names-vs-synchronized-standby-slots/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://kylorend3r.github.io/posts/synchronous-standby-names-vs-synchronized-standby-slots/</guid><description>Understanding why synchronous_standby_names and synchronized_standby_slots are independent in PostgreSQL, and how misconfiguring them together can silently break your HA setup</description></item></channel></rss>