| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | github kran <githubkran(at)gmail(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: AutoVacuum and growing transaction XID's |
| Date: | 2020-05-08 21:11:04 |
| Message-ID: | CAHOFxGpH-+ayDCqBekhCp4eU0ZWtRK4ob9nRs6_8zQXdC95HFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
autovacuum_naptime being only 5 seconds seems too frequent. A lock_timeout
might be 1-5 seconds depending on your system. Usually, DDL can fail and
wait a little time rather than lock the table for minutes and have all
reads back up behind the DDL.
Given you have autovacuum_vacuum_cost_limit set to unlimited (seems very
odd), I'm not sure a manual vacuum freeze command on the tables with high
age would perform differently. Still, issuing a vacuum freeze and then
killing the autovacuum process might be worth trying.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-05-08 21:28:42 | Re: pg_basebackup cannot compress to STDOUNT |
| Previous Message | Rob Sargent | 2020-05-08 21:05:08 | Re: Thoughts on how to avoid a massive integer update. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arya F | 2020-05-10 04:10:20 | Re: 600 million rows of data. Bad hardware or need partitioning? |
| Previous Message | Jeff Janes | 2020-05-08 13:54:25 | Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. |