| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Aaron Pelz <aaronepelz(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupt index stopping autovacuum system wide |
| Date: | 2019-07-17 19:58:35 |
| Message-ID: | CAH2-Wz=3Sz0hARDUVVN_j4m8Pj6yb5meDejnQJZBk5MU5hVjvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 17, 2019 at 10:27 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> > It's possible that amcheck would have given you an accurate diagnosis
> > of the problem -- especially if you used bt_index_parent_check():
> >
> > https://www.postgresql.org/docs/current/amcheck.html
>
> BTW, be sure to use the 'heapallindexed' option with
> bt_index_parent_check() to detect missing downlinks, which is exactly
> the problem that VACUUM complained about.
Can you tell us more about this index? Can you share its definition
(i.e. what does \d show in psql)?
Is it an expression index, or a partial index? A composite? What
datatypes are indexed?
Thanks
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-07-17 22:14:21 | Re: Corrupt index stopping autovacuum system wide |
| Previous Message | Peter Geoghegan | 2019-07-17 19:40:20 | Re: Corrupt index stopping autovacuum system wide |