| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Aaron Pelz <aaronepelz(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupt index stopping autovacuum system wide |
| Date: | 2019-07-17 16:57:10 |
| Message-ID: | 24777.1563382630@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> 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.
It looks that way, but how would a broken non-shared index have held up
autovacuuming in other databases? Maybe, as this one's xmin horizon
got further and further behind, the launcher eventually stopped
considering launching workers into any other databases? That seems
like a bad thing; it's postponing work that will need to be done
eventually.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sonam Sharma | 2019-07-17 17:03:05 | Change in db size |
| Previous Message | Aaron Pelz | 2019-07-17 16:27:21 | Re: Corrupt index stopping autovacuum system wide |