<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PgBackRest on Farid</title><link>https://polymatx.dev/blog/tags/pgbackrest/</link><description>Recent content in PgBackRest on Farid</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://polymatx.dev/blog/tags/pgbackrest/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres High Availability on Hetzner, Step by Step: Patroni, etcd, PgBouncer, pgBackRest and a Load Balancer</title><link>https://polymatx.dev/blog/posts/postgres-ha-patroni-hetzner/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate><guid>https://polymatx.dev/blog/posts/postgres-ha-patroni-hetzner/</guid><description>&lt;p&gt;This is the procedure I used to move a production billing database from a single server onto a Postgres HA cluster on Hetzner Cloud, written as steps you can follow. Every configuration file below is the one running in production today, with names and secrets replaced and a few tuning parameters trimmed for length. The cluster has been through ten real leader changes since it went live.&lt;/p&gt;
&lt;p&gt;Stack: PostgreSQL 16.15, Patroni 4.1.5, etcd 3.4.30, PgBouncer 1.25.2, pgBackRest 2.59.1, Ubuntu 24.04, Hetzner Cloud servers, Volumes, Object Storage and a Load Balancer.&lt;/p&gt;</description></item></channel></rss>