Re: Corrupted btree index on HEAD because of covering indexes

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
Subject: Re: Corrupted btree index on HEAD because of covering indexes
Date: 2018-04-20 01:27:50
Message-ID: 20180420012607.GG2024@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 19, 2018 at 10:47:02PM +0300, Teodor Sigaev wrote:
> I tried to minimize Michael's test case and add it to patch.

I cannot comment on the actual fix as I lack background in the area, but
having a test case and even more having pg_upgrade do some work on those
pages are good things. This addresses the failure as far as I can see.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian.long@i-soft.com.cn 2018-04-20 02:00:38 Re: Re: Is there a memory leak in commit 8561e48?
Previous Message Peter Geoghegan 2018-04-20 01:26:49 Re: Corrupted btree index on HEAD because of covering indexes