| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Justin King <kingpin867(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG12 autovac issues |
| Date: | 2020-03-20 19:17:16 |
| Message-ID: | CAHOFxGpeKDaDcC-fj377Q5L8DRFs49jDvo4Cs5iySGrDUwZBQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
>
> We haven't isolated *which* table it is blocked on (assuming it is),
> but all autovac's cease running until we manually intervene.
>
> When we get into this state again, is there some other information
> (other than what is in pg_stat_statement or pg_stat_activity) that
> would be useful for folks here to help understand what is going on?
https://www.postgresql.org/docs/current/progress-reporting.html#VACUUM-PROGRESS-REPORTING
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kurt Roeckx | 2020-03-20 21:50:53 | Append only tables |
| Previous Message | Andres Freund | 2020-03-20 19:03:17 | Re: PG12 autovac issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Magoffin | 2020-03-20 20:32:39 | Re: Duplicate key violation on upsert |
| Previous Message | Adrian Klaver | 2020-03-20 19:10:34 | Re: Duplicate key violation on upsert |