| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Олег Самойлов <splarv(at)ya(dot)ru>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: autoanalyze did not run |
| Date: | 2026-01-26 07:23:19 |
| Message-ID: | c6b71dd5f6839962adef8b1481d9de348ccce661.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
> 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?
Is "track_activities" set to "on"?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2026-01-26 12:14:36 | Re: autoanalyze did not run |
| Previous Message | Олег Самойлов | 2026-01-26 05:31:24 | autoanalyze did not run |