From: | Justin King <kingpin867(at)gmail(dot)com> |
---|---|
To: | Michael Lewis <mlewis(at)entrata(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Fwd: PG12 autovac issues |
Date: | 2020-03-19 15:31:44 |
Message-ID: | CAE39h21ajCR6gEVM2scm2ApfLG9VUHb++W3MWuw=SP4V5o_cXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Wed, Mar 18, 2020 at 1:40 PM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
>
> Do you have default fillfactor set on this table? If not, I would wonder if reducing it to 50% or even 20% would allow many more HOT updates that would reduce bloat.
I don't believe we have a default fillfactor, but I'm still trying to
understand why autovacs would completely stop -- that seems like a
bug. Especially since there was no change between PG10 and PG12 and
this problem never existed there.
> Also, is there any period of lower activity on your system that you could schedule a vacuum freeze for daily or weekly? I believe having frozen pages would also mean all the autovacuums would be able to skip more pages and therefore be faster.
>
> >> autovacuum_vacuum_cost_delay = 20
>
> This was changed to 2ms in PG12. You should reduce that most likely.
Actually, we set that back from 2ms > 20ms to replicate what PG10 was
doing just in case it had an impact (spoiler: it did not).
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2020-03-19 16:02:01 | Re: Fwd: PG12 autovac issues |
Previous Message | Justin King | 2020-03-19 15:25:25 | Re: Re: PG12 autovac issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2020-03-19 16:02:01 | Re: Fwd: PG12 autovac issues |
Previous Message | Justin King | 2020-03-19 15:25:25 | Re: Re: PG12 autovac issues |