Re: autoanalyze did not run - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: autoanalyze did not run
Date
Msg-id 04dc073cd84313cb9b711833f905a07d099a5f28.camel@cybertec.at
Whole thread Raw
In response to Re: autoanalyze did not run  (Олег Самойлов <splarv@ya.ru>)
List pgsql-admin
On Mon, 2026-01-26 at 17:35 +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.
> > >
> > > 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.

Then the only explanation is that all autovacuum workers are active, and this
table is starved.  See how many autovacuum workers are visible in pg_stat_activity
and compare that to autovacuum_max_workers.

Yours,
Laurenz Albe



pgsql-admin by date:

Previous
From: Олег Самойлов
Date:
Subject: Re: autoanalyze did not run
Next
From: Kristjan Mustkivi
Date:
Subject: Re: autoanalyze did not run