Re: Corrupt index stopping autovacuum system wide - Mailing list pgsql-general

From Aaron Pelz
Subject Re: Corrupt index stopping autovacuum system wide
Date
Msg-id CAHqUQycKBNTzjfeujFe5U70BuqNh2V_mX-jFtBpavccWVdSpUw@mail.gmail.com
Whole thread Raw
In response to Re: Corrupt index stopping autovacuum system wide  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Corrupt index stopping autovacuum system wide
List 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@bowt.ie> wrote:
On Wed, Jul 17, 2019 at 10:27 AM Peter Geoghegan <pg@bowt.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

pgsql-general by date:

Previous
From: Dirk Riehle
Date:
Subject: Re: PostgreSQL as a Service
Next
From: Peter Geoghegan
Date:
Subject: Re: Corrupt index stopping autovacuum system wide