<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident-Report on PIGSTY</title><link>https://pigsty.io/tags/incident-report/</link><description>Recent content in Incident-Report on PIGSTY</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Apr 2026 09:14:36 +0800</lastBuildDate><atom:link href="https://pigsty.io/tags/incident-report/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Use pg_filedump for Data Recovery?</title><link>https://pigsty.io/blog/pg/pg-filedump/</link><pubDate>Wed, 27 Sep 2023 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/pg-filedump/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/pg-filedump/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/pg-filedump.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Backups are a DBA&amp;rsquo;s lifeline — but what if your PostgreSQL database has already exploded and you have no backups? Maybe &lt;code&gt;pg_filedump&lt;/code&gt; can help you! &lt;a href="https://vonng.com/en/pg/pg-filedump/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Incident-Report: Patroni Failure Due to Time Travel</title><link>https://pigsty.io/blog/pg/time-travel/</link><pubDate>Mon, 22 Feb 2021 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/time-travel/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/time-travel/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/time-travel.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Machine restarted due to failure, NTP service corrected PG time after PG startup, causing Patroni to fail to start. &lt;a href="https://vonng.com/en/pg/time-travel/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Incident: PostgreSQL Extension Installation Causes Connection Failure</title><link>https://pigsty.io/blog/pg/extension/</link><pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/extension/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/extension/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/extension.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Today encountered an interesting case where a customer reported database connection issues caused by extensions. &lt;a href="https://vonng.com/en/pg/extension/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Incident-Report: Connection-Pool Contamination Caused by pg_dump</title><link>https://pigsty.io/blog/pg/pg-dump-failure/</link><pubDate>Tue, 11 Dec 2018 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/pg-dump-failure/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/pg-dump-failure/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/pg-dump-failure.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Sometimes, interactions between components manifest in subtle ways. For example, using pg_dump to export data from a connection pool can cause connection pool contamination issues. &lt;a href="https://vonng.com/en/pg/pg-dump-failure/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>PostgreSQL Data Page Corruption Repair</title><link>https://pigsty.io/blog/pg/page-corruption/</link><pubDate>Thu, 29 Nov 2018 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/page-corruption/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/page-corruption/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/page-corruption.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Using binary editing to repair PostgreSQL data pages, and how to make a primary key query return two records. &lt;a href="https://vonng.com/en/pg/page-corruption/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Incident-Report: Integer Overflow from Rapid Sequence Number Consumption</title><link>https://pigsty.io/blog/pg/sequence-overflow/</link><pubDate>Fri, 20 Jul 2018 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/sequence-overflow/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/sequence-overflow/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/sequence-overflow.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you use Integer sequences on tables, you should consider potential overflow scenarios. &lt;a href="https://vonng.com/en/pg/sequence-overflow/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Incident-Report: PostgreSQL Transaction ID Wraparound</title><link>https://pigsty.io/blog/pg/xid-wrap-around/</link><pubDate>Fri, 20 Jul 2018 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/xid-wrap-around/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/xid-wrap-around/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/xid-wrap-around.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;XID WrapAround is perhaps a unique type of failure specific to PostgreSQL &lt;a href="https://vonng.com/en/pg/xid-wrap-around/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Incident-Report: Uneven Load Avalanche</title><link>https://pigsty.io/blog/pg/download-failure/</link><pubDate>Sun, 08 Apr 2018 00:00:00 +0000</pubDate><guid>https://pigsty.io/blog/pg/download-failure/</guid><description>&lt;p&gt;&lt;a href="https://vonng.com/en/pg/download-failure/"&gt;&lt;img src="https://pigsty.io/img/hero/pg/download-failure.jpg" alt="featured"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Recently there was a perplexing incident where a database had half its data volume and load migrated away, but ended up being overwhelmed due to increased load. &lt;a href="https://vonng.com/en/pg/download-failure/"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>