From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: |
Date: | 2019-09-24 21:04:27 |
Message-ID: | CAH2-WzkSSbFSDUiD7qtLZ2sAqy9Tev-GteTiAnO-w7mZeGkqeg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Sep 24, 2019 at 1:55 PM Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> wrote:
> I inspected both values to the best of my abilities and found them equal byte-to byte.
I would try running contrib/amcheck, which should be able to confirm
index corruption, and give you a specific complaint. You may then be
able to inspect the exact index page with the problem using
contrib/pageinspect. Something like this ought to do it on Postgres
10:
CREATE EXTENSION IF NOT EXISTS amcheck
SELECT bt_index_check('vocabulary_phrase_key');
If that doesn't show any errors, then perhaps try this:
SELECT bt_index_parent_check('vocabulary_phrase_key');
Let us know what you see. We may be able to offer additional guidance,
depending on how that goes.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Alfred R. Fuller | 2019-09-24 21:50:54 | Re: Bug with "CHECK" when part of ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... CHECK ... |
Previous Message | Vladimir Ryabtsev | 2019-09-24 21:01:09 | Violation of a unique key? |