Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"

From: Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
Date: 2019-02-14 07:56:36
Message-ID: CA+t6e1m7g309O=P6p4jSkxZUa45MGEc_A3+fvuF69Mv-cvK8cw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I meant the anaylze, if anaylze will run very often on the original table,
arent there disadvantages for it ?

‫בתאריך יום ד׳, 13 בפבר׳ 2019 ב-18:54 מאת ‪Alvaro Herrera‬‏ <‪
alvherre(at)2ndquadrant(dot)com‬‏>:‬

> On 2019-Feb-13, Mariel Cherkassky wrote:
>
> > To be honest, it isnt my db, but I just have access to it ...
>
> Well, I suggest you forget the password then :-)
>
> > Either way, so I need to change the vacuum_Analyze_scale/threshold for
> the
> > original table ? But the value will be too high/low for the original
> table.
> > For example if my original table has 30,000 rows and my toasted has
> > 100,000,000 rows. I want to analyze every 50K records in the toasted (by
> > the way, sounds legit ?) which is 0.05% of 100m. With this value it means
> > that every 0.05*30,000=1500 updated/deletes on the original table it will
> > run analyze on the original table which is very often...
> > Doesn't it seems a little bit problematic ?
>
> Autovacuum considers main table and toast table separately for
> vacuuming, so nothing you do to the parameters for the main table will
> affect the vacuuming schedule of the toast table.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message suganthi Sekar 2019-02-14 09:38:52 Re: server hardware tuning.
Previous Message Alvaro Herrera 2019-02-13 16:54:45 Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"