Date: Thu, 28 Oct 2021 15:01:24 -0700
From: Andres Freund <andres@anarazel.de>
To: Kamigishi Rei <iijima.yun@koumakan.jp>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>,
	Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Peter Geoghegan <pg@bowt.ie>,
	PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>,
	Thomas Munro <thomas.munro@gmail.com>
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Message-ID: <20211028220124.n4vulzxp6i6fsq4t@alap3.anarazel.de>
References: <202110250104.jve5vzdedck7@alvherre.pgsql>
 <87h7d57b3q.fsf@news-spur.riddles.org.uk>
 <20211028214209.kbv4ulehz36up6kq@alap3.anarazel.de>
 <125603c4-4403-dcbb-221e-fd1d4ef6ed83@koumakan.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <125603c4-4403-dcbb-221e-fd1d4ef6ed83@koumakan.jp>
Archived-At: 
 <https://www.postgresql.org/message-id/20211028220124.n4vulzxp6i6fsq4t%40alap3.anarazel.de>
Precedence: bulk

Hi,

On 2021-10-29 00:46:29 +0300, Kamigishi Rei wrote:
> The issue manifested again earlier today *after* a REINDEX followed by
> enabling WAL replica logging on the 24th of October. I saved a snapshot of
> the filesystem holding the data directory. Would that be useful for further
> analysis?

Yes, that's *quite* useful.  I assume you can't just share that snapshot?

Once we identified an affected heap and index page with the corruption, we
should use pg_waldump to scan for all chanes to that table.

Do you have the log file(s) from between the 24th and now? That might give us
a good starting point for the LSN range to scan.

Greetings,

Andres Freund