| From: | github kran <githubkran(at)gmail(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(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-12 15:40:25 |
| Message-ID: | CACaZr5T4P8oo45gvqOKn8CrAatGr-POW0=jpHzEXZ4zn5U3mCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Thanks for yous suggestions Michael and David.
On Fri, May 8, 2020 at 4:11 PM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
> 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 | Michael Lewis | 2020-05-12 15:51:27 | Re: Hash partitioning, what function is used to compute the hash? |
| Previous Message | Laurenz Albe | 2020-05-12 15:29:50 | Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Pritchard | 2020-05-13 09:33:35 | Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join |
| Previous Message | Arya F | 2020-05-10 04:10:20 | Re: 600 million rows of data. Bad hardware or need partitioning? |