timescaledb log_autovacuum_min_duration: 0 settings creates so many logs

[ismailyenigul]

postgresql settings log_autovacuum_min_duration: 0 at https://github.com/timescale/timescaledb-kubernetes/blob/master/charts/timescaledb-single/values.yaml#L140 creates too many events for every autovacuum activities. It creates one event for each hypertable
log_autovacuum_min_duration: 0 means log all autovacuum events.

It is disabled by default in default postgresql.conf and we can disable it too in the chart values.

Default value:

#log_autovacuum_min_duration = -1	# -1 disables, 0 logs all actions and

Here is the sample logs

_internal._hyper_535_37056_chunk" system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.04 s
2020-05-20 23:26:55 UTC [19097]: [5ec5bcb0.4a99-103] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_575_37082_chunk" system usage: CPU: user: 0.05 s, system: 0.00 s, elapsed: 0.19 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-104] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_625_37088_chunk" system usage: CPU: user: 0.06 s, system: 0.01 s, elapsed: 0.30 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-105] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_739_37097_chunk" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.04 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-106] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_1605_37199_chunk" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-107] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_1431_37232_chunk" system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.04 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-108] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_1413_37230_chunk" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-109] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_2185_37241_chunk" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-110] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_2201_37242_chunk" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2020-05-20 23:26:56 UTC [19097]: [5ec5bcb0.4a99-111] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_1613_37283_chunk" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2020-05-20 23:26:57 UTC [19097]: [5ec5bcb0.4a99-112] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_1491_37315_chunk" system usage: CPU: user: 0.02 s, system: 0.00 s, elapsed: 0.07 s
2020-05-20 23:26:57 UTC [19097]: [5ec5bcb0.4a99-113] @,app= [00000] LOG:  automatic analyze of table "postgres._timescaledb_internal._hyper_1421_37

[feikesteenbergen]

Probably best to limit it by default to only log longer vacuums.

I'm thinking of 60 seconds, does that sound reasonable?

(That would skip most vacuums, a typical hypertable would only do autoanalyzes, as no deletes/updates are done, analyzes should be quick)

[ismailyenigul]

yes
I think 60 secs reasonable.

[feikesteenbergen]

Default has changed in https://github.com/timescale/timescaledb-kubernetes/releases/tag/v0.6.2