| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Karthik Jagadish (kjagadis)" <kjagadis(at)cisco(dot)com>, Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Chandruganth Ayyavoo Selvam (chaayyav)" <chaayyav(at)cisco(dot)com>, "Prasanna Satyanarayanan (prassaty)" <prassaty(at)cisco(dot)com>, "Jaganbabu M (jmunusam)" <jmunusam(at)cisco(dot)com>, "Joel Mariadasan (jomariad)" <jomariad(at)cisco(dot)com> |
| Subject: | Re: Postgres auto vacuum - Disable |
| Date: | 2022-11-07 13:22:56 |
| Message-ID: | 1f6bbc193eadfec408e206c7d0836d935b65e965.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikita Malakhov | 2022-11-07 13:30:32 | Re: collect_corrupt_items_vacuum.patch |
| Previous Message | Antonin Houska | 2022-11-07 13:19:42 | Re: refactor ownercheck and aclcheck functions |