| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 17:18:19 |
| Message-ID: | CAH2-WzmYJ_XuKQZWEeY34vYz_aqjV3MSAYprpCyvQ50r3_BWWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 17, 2019 at 9:57 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
I don't know exactly how the launcher would behave offhand, but it's
clear that not being able to VACUUM one table in one database (because
it has a corrupt index) ultimately risks the availability of every
database in the cluster. Many installations receive little to no
supervision, so it may just be a matter of time there. That is
certainly a bad thing.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-07-17 17:27:10 | Re: Corrupt index stopping autovacuum system wide |
| Previous Message | Vijaykumar Jain | 2019-07-17 17:15:52 | Re: [External] Change in db size |