Re: BUG #17245: Index corruption involving deduplicated entries - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #17245: Index corruption involving deduplicated entries
Date
Msg-id CAH2-WzksOK6mrNrRmgPeyvZRJu-tuSZpjbfamjqR56MbUP61Dw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17245: Index corruption involving deduplicated entries  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: BUG #17245: Index corruption involving deduplicated entries
List pgsql-bugs
On Sun, Oct 24, 2021 at 3:11 PM Peter Geoghegan <pg@bowt.ie> wrote:
> On Sun, Oct 24, 2021 at 2:35 PM K. R. <iijima.yun@koumakan.jp> wrote:
> > $ ./pg_amcheck -U postgres --heapallindexed --parent-check --rootdescend
> > azurlane_wiki
> > btree index "azurlane_wiki.mediawiki.page_redirect_namespace_len":
> >      ERROR:  posting list contains misplaced TID in index
> > "page_redirect_namespace_len"
> >      DETAIL:  Index tid=(14,9) posting list offset=110 page lsn=2/2C4F7CD8.
> > btree index "azurlane_wiki.mediawiki.page_len":
> >      ERROR:  posting list contains misplaced TID in index "page_len"
> >      DETAIL:  Index tid=(1,2) posting list offset=34 page lsn=2/2DDA2378.
> > btree index "azurlane_wiki.mediawiki.transcode_key_idx":
> >      ERROR:  posting list contains misplaced TID in index
> > "transcode_key_idx"
> >      DETAIL:  Index tid=(1,9) posting list offset=5 page lsn=2/2B53AED8.

Does it make any difference if you run "./pg_amcheck -U postgres
--heapallindexed azurlane_wiki" instead?

Typically I would expect this to be less interesting, because you're
asking pg_amcheck to do less checking. But this is not a typical case.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Next
From: Noah Misch
Date:
Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data