<?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>Pg_init_privs on kylorend3r Blog</title><link>https://kylorend3r.github.io/tags/pg_init_privs/</link><description>Recent content in Pg_init_privs 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>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kylorend3r.github.io/tags/pg_init_privs/index.xml" rel="self" type="application/rss+xml"/><item><title>What It Actually Takes to Upgrade PostgreSQL in Production Without Breaking Everything</title><link>https://kylorend3r.github.io/posts/postgresql-major-upgrade-pg13-to-pg18-lessons-learned/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://kylorend3r.github.io/posts/postgresql-major-upgrade-pg13-to-pg18-lessons-learned/</guid><description>A practical guide to planning and executing a PostgreSQL major version upgrade at scale: why we upgraded, how we designed the playbook, why the process was still dangerous, and two real bugs we discovered, reported to the community, and solved.</description></item></channel></rss>