Thread: bug in autovacuum_analyze_scale_factor meta data
This is what I have in postgres 10 pg_settings table: and the documentation has different description. What's more the default value is outside the range of the min/max value.
-[ RECORD 2 ]---+------------------------------------------------------------------------------------------
name | autovacuum_analyze_scale_factor
setting | 0.1
unit | [NULL]
category | Autovacuum
short_desc | Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples.
extra_desc | [NULL]
context | sighup
vartype | real
source | default
min_val | 0
max_val | 100
enumvals | [NULL]
boot_val | 0.1
reset_val | 0.1
sourcefile | [NULL]
sourceline | [NULL]
pending_restart | f
name | autovacuum_analyze_scale_factor
setting | 0.1
unit | [NULL]
category | Autovacuum
short_desc | Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples.
extra_desc | [NULL]
context | sighup
vartype | real
source | default
min_val | 0
max_val | 100
enumvals | [NULL]
boot_val | 0.1
reset_val | 0.1
sourcefile | [NULL]
sourceline | [NULL]
pending_restart | f
regards,
Szymon Lipiński
On 10/31/18 6:58 AM, Szymon Lipiński wrote: > This is what I have in postgres 10 pg_settings table: and the > documentation has different description. What's more the default value > is outside the range of the min/max value. Not seeing it: 0 < 0.1 < 100 reltuples is a measure of the sixe of the table: https://www.postgresql.org/docs/11/static/catalog-pg-class.html "reltuples float4 Number of live rows in the table. This is only an estimate used by the planner. It is updated by VACUUM, ANALYZE, and a few DDL commands such as CREATE INDEX. " > > -[ RECORD 2 > ]---+------------------------------------------------------------------------------------------ > name | autovacuum_analyze_scale_factor > setting | 0.1 > unit | [NULL] > category | Autovacuum > short_desc | Number of tuple inserts, updates, or deletes prior to > analyze as a fraction of reltuples. > extra_desc | [NULL] > context | sighup > vartype | real > source | default > min_val | 0 > max_val | 100 > enumvals | [NULL] > boot_val | 0.1 > reset_val | 0.1 > sourcefile | [NULL] > sourceline | [NULL] > pending_restart | f > > regards, > Szymon Lipiński -- Adrian Klaver adrian.klaver@aklaver.com
Yep, I messed a couple of options, I'm sorry.
regards,
Szymon Lipiński
On Wed, 31 Oct 2018 at 15:07, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 10/31/18 6:58 AM, Szymon Lipiński wrote:
> This is what I have in postgres 10 pg_settings table: and the
> documentation has different description. What's more the default value
> is outside the range of the min/max value.
Not seeing it:
0 < 0.1 < 100
reltuples is a measure of the sixe of the table:
https://www.postgresql.org/docs/11/static/catalog-pg-class.html
"reltuples float4 Number of live rows in the table. This is only an
estimate used by the planner. It is updated by VACUUM, ANALYZE, and a
few DDL commands such as CREATE INDEX.
"
>
> -[ RECORD 2
> ]---+------------------------------------------------------------------------------------------
> name | autovacuum_analyze_scale_factor
> setting | 0.1
> unit | [NULL]
> category | Autovacuum
> short_desc | Number of tuple inserts, updates, or deletes prior to
> analyze as a fraction of reltuples.
> extra_desc | [NULL]
> context | sighup
> vartype | real
> source | default
> min_val | 0
> max_val | 100
> enumvals | [NULL]
> boot_val | 0.1
> reset_val | 0.1
> sourcefile | [NULL]
> sourceline | [NULL]
> pending_restart | f
>
> regards,
> Szymon Lipiński
--
Adrian Klaver
adrian.klaver@aklaver.com