<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recovery Engineering on Brian Faust</title><link>https://vacua.dev/series/recovery-engineering/</link><description>Recent content in Recovery Engineering on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vacua.dev/series/recovery-engineering/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Backup Is Only an Input to Recovery</title><link>https://vacua.dev/thoughts/a-backup-is-only-an-input-to-recovery/</link><pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate><guid>https://vacua.dev/thoughts/a-backup-is-only-an-input-to-recovery/</guid><description>&lt;p&gt;The backup job is green. The archive exists, its checksum matches, and
&lt;code&gt;pg_restore&lt;/code&gt; exits successfully. A shipment lookup still returns nothing.&lt;/p&gt;
&lt;p&gt;That is not a hypothetical combination. The &lt;a href="https://vacua.dev/reproductions/ops-03/"&gt;OPS-03 fixture&lt;/a&gt;

contains a schema-only archive with a stable SHA-256 identity. PostgreSQL
restores it without error. The tables and constraints exist. The application
probe then asks for &lt;code&gt;shipment-100&lt;/code&gt;, receives no row, and rejects the recovery.&lt;/p&gt;
&lt;p&gt;The checksum answered which bytes we selected. The restore command answered
whether PostgreSQL could apply them. Neither answered whether the recovered
database could do useful work.&lt;/p&gt;</description></item></channel></rss>