<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>postgres on dominik.suess.wtf</title><link>https://dominik.suess.wtf/filetags/postgres/</link><description>Recent content in postgres on dominik.suess.wtf</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 25 May 2026 11:28:15 +0200</lastBuildDate><atom:link href="https://dominik.suess.wtf/filetags/postgres/index.xml" rel="self" type="application/rss+xml"/><item><title>requested timeline is not a child of this servers history</title><link>https://dominik.suess.wtf/notes/20260521t140758/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://dominik.suess.wtf/notes/20260521t140758/</guid><description>&lt;p&gt;
This sometimes happens to me if my wonky cluster decides to not behave. My original solution was to create a backup and then rebuild the cluster from this but I found a better solution in [[&lt;a href="https://github.com/cloudnative-pg/cloudnative-pg/issues/4188#issuecomment-2912459078][this"&gt;https://github.com/cloudnative-pg/cloudnative-pg/issues/4188#issuecomment-2912459078][this&lt;/a&gt; comment]:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I solved the issue.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You need to check the last history file on your primary ls -1 /var/lib/postgresql/wal/pg_wal/*.history. In my case it is /var/lib/postgresql/wal/pg_wal/00000015.history&lt;/li&gt;
&lt;li&gt;Go to S3 storage and delete everything, which starts with next numbers: 00000016*, 00000017*, 00000018* and so on&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Looks like it gets wrong history (which was canceled before) and fails&lt;/p&gt;</description></item></channel></rss>