On Mon, 2022-11-07 at 12:12 +0000, Karthik Jagadish (kjagadis) wrote: > I have follow-up question where the vacuum process is waiting and not doing > it’s job. > When we grep on waiting process we see below output. Whenever we see this we > notice > that the vacuum is not happening and the system is running out of space. > > [root@zpah0031 ~]# ps -ef | grep 'waiting' > postgres 8833 62646 0 Jul28 ? 00:00:00 postgres: postgres cgms > [local] VACUUM waiting > postgres 18437 62646 0 Jul27 ? 00:00:00 postgres: postgres cgms > [local] VACUUM waiting > > > What could be the reason as to why the vacuum is not happening? Is it because > some lock is > present in the table/db or any other reason?
Look in "pg_stat_activity". I didn't check, but I'm sure it's the intentional break configured with "autovacuum_vacuum_cost_delay". Reduce that parameter for more autovacuum speed. Yours, Laurenz Albe
