From: | Michael Lewis <mlewis(at)entrata(dot)com> |
---|---|
To: | Justin King <kingpin867(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Fwd: PG12 autovac issues |
Date: | 2020-03-19 16:02:01 |
Message-ID: | CAHOFxGr+tUxRA=SozSgms4LrQ34DBF9LohYr2VF+uBg7sOj2Eg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Thu, Mar 19, 2020 at 9:31 AM Justin King <kingpin867(at)gmail(dot)com> wrote:
> 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.
>
Is there any reason to not schedule vacuum freeze for each db daily? Just
curious.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin King | 2020-03-19 16:55:13 | Re: Fwd: PG12 autovac issues |
Previous Message | Justin King | 2020-03-19 15:31:44 | Re: Fwd: PG12 autovac issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Justin King | 2020-03-19 16:55:13 | Re: Fwd: PG12 autovac issues |
Previous Message | Justin King | 2020-03-19 15:31:44 | Re: Fwd: PG12 autovac issues |