26.01.2026 10:23, Laurenz Albe пишет:
On Mon, 2026-01-26 at 08:31 +0300, Олег Самойлов wrote:
I try to investigate why autoanalyze did not run in time of our initial
loading data. Yes, I know, running analyze manually is highly
recommended in such case. But is must run automatically too.
You'd have to show more evidence that this is a bug, or provide a way
to reproduce the problem.
I need to narrow my case, that why I need to know on what exactly depends (on what column) the launching the autoexplain.
select relid::regclass, n_live_tup, n_tup_ins, n_tup_upd,
n_mod_since_analyze from pg_stat_user_tables as s join pg_class as c on
(s.relid=c.oid) where s.autoanalyze_count=0 and relkind='r' and
n_live_tup>0 limit 1;
-[ RECORD 1 ]-------+----------
relid | addresses
n_live_tup | 13844405
n_tup_ins | 0
n_tup_upd | 0
n_mod_since_analyze | 0
PostgreSQL 17.7 (Debian 17.7-3.pgdg13+1) on x86_64-pc-linux-gnu,
compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit (from PGDG)
Are you sure that you committed the transaction?
I am very sure, thats why there are 13844347 rows in that table. By single copy.
Is "track_activities" set to "on"?
I checked, yep.
Yours,
Laurenz Albe
