Re: BUG #17245: Index corruption involving deduplicated entries

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "K(dot) R(dot)" <iijima(dot)yun(at)koumakan(dot)jp>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Date: 2021-10-26 22:23:49
Message-ID: CAH2-WzmvKN8TB3wZEdnub+pVU3Vv_5KQW_wqxtqEjyN8C9pwSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Oct 26, 2021 at 1:36 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> A few more questions for you, if you don't mind:
>
> 1. Can you tell me which tables the 4 known-corrupt indexes
> (page_redirect_namespace_len, page_len, transcode_key_idx, and
> page_main_title) are defined against?
> 2. Can you show me the definition of the table or tables, using \d from psql?
> 3. Do you notice any consistent pattern here? For example, are foreign
> keys involved?
> 4. How do the table or tables tend to get updated?

Also:

5. Do you use CREATE INDEX CONCURRENTLY or REINDEX CONCURRENTLY much?

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-10-27 00:53:37 Re: conchuela timeouts since 2021-10-09 system upgrade
Previous Message Thomas Munro 2021-10-26 20:45:38 Re: conchuela timeouts since 2021-10-09 system upgrade