https://sow.pgsty.com/tags/recovery/ Recent content in recovery on SOW Hugo en Thu, 15 Oct 2026 17:53:46 +0800 https://sow.pgsty.com/docs/reference/troubleshooting/ Mon, 01 Jan 0001 00:00:00 +0000 https://sow.pgsty.com/docs/reference/troubleshooting/ <p>Start with the error message and the <a href="https://sow.pgsty.com/docs/reference/exit-codes/">exit code</a>. For Managed commands, specify the workspace and Repository so you inspect the intended state:</p> <div class="td-code td-code--untitled" id="td-code-a6e41240-fence-0" data-td-code data-td-code-auto-id data-td-language="bash" data-td-line-count="3"> <div class="td-code__viewport" id="td-code-a6e41240-fence-0-viewport" data-td-code-viewport><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sow version </span></span><span class="line"><span class="cl">sow status -C /srv/sow -r pgsql </span></span><span class="line"><span class="cl">sow log -C /srv/sow -r pgsql</span></span></code></pre></div></div> </div> <p>Replace <code>/srv/sow</code>, <code>pgsql</code>, and the target name <code>prod</code> below with your configuration.</p> <h2 id="the-database-needs-migration">The database needs migration </h2> <p>After upgrading a 0.3 or 0.4 workspace to 0.5, stop workspace writers and back up the complete workspace. Then run:</p>