| 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 16:21:06 |
| Message-ID: | CAH2-Wz=ggW6uaepx-9riyedENaf-2LRxs89bmU1fd6i0D8F4jQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 17, 2019 at 8:54 AM Aaron Pelz <aaronepelz(at)gmail(dot)com> wrote:
> To me it looks like a *single* corrupt index held up autovacuums across our entire server, even other in other databases on the same server. Am I interpreting this correctly?
Yes -- that is correct.
What PostgreSQL version are you on? Was this an INCLUDE index on PostgreSQL 11?
> Would love guidance on diagnosing this type of thing and strategies for preventing it.
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
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Pelz | 2019-07-17 16:27:21 | Re: Corrupt index stopping autovacuum system wide |
| Previous Message | Aaron Pelz | 2019-07-17 15:53:58 | Corrupt index stopping autovacuum system wide |