Re: Fwd: PG12 autovac issues

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 16:55:13
Message-ID: CAE39h20++-ab=2GaTNbOj_KRYTm2_1g4p=aYaBHBod5XuTHmAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

On Thu, Mar 19, 2020 at 11:02 AM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
>
> 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.

No, not really -- it just feels like a bandaid for something that
should (and was) working already. It is possible where I'm headed,
but I just thought I'd reach out to the community to see if anyone has
seen or could think of a reason why this might have started by moving
from PG10 > PG12 and whether it was some possible regression.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Andres Freund 2020-03-19 22:35:20 Re: PG12 autovac issues
Previous Message Michael Lewis 2020-03-19 16:02:01 Re: Fwd: PG12 autovac issues

Browse pgsql-general by date

  From Date Subject
Next Message pabloa98 2020-03-19 21:36:54 Could postgres12 support millions of sequences? (like 10 million)
Previous Message Michael Lewis 2020-03-19 16:02:01 Re: Fwd: PG12 autovac issues