Re: Corrupt index stopping autovacuum system wide

From: Aaron Pelz <aaronepelz(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Corrupt index stopping autovacuum system wide
Date: 2019-07-18 16:06:43
Message-ID: CAHqUQycKBNTzjfeujFe5U70BuqNh2V_mX-jFtBpavccWVdSpUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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?

It's a simple btree expression on a geometry(Point,4326) , no expression no
partial no composite.

On Wed, Jul 17, 2019 at 3:58 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> 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
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2019-07-18 16:21:23 Re: Corrupt index stopping autovacuum system wide
Previous Message Dirk Riehle 2019-07-18 16:03:39 Re: PostgreSQL as a Service