| From: | "Karthik Jagadish (kjagadis)" <kjagadis(at)cisco(dot)com> |
|---|---|
| To: | "pgsql-user(at)postgresql(dot)org" <pgsql-user(at)postgresql(dot)org> |
| Cc: | "Prasanna Satyanarayanan (prassaty)" <prassaty(at)cisco(dot)com>, "Chandruganth Ayyavoo Selvam (chaayyav)" <chaayyav(at)cisco(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Index not getting cleaned even though vacuum is running |
| Date: | 2022-11-15 15:38:47 |
| Message-ID: | IA1PR11MB6170DCAF11B76E01972775A8D8049@IA1PR11MB6170.namprd11.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
We notice that vacuum is happening at regular intervals but the space occupied by indexes is always increasing. Any pointers as to why would this happen?
Some outputs below. Auto vacuum is enabled but we notice index size is growing.
$ psql -U postgres -d cgms -c "SELECT pg_size_pretty(SUM(pg_relation_size(table_schema||'.'||table_name))) as size from information_schema.tables"
size
-------
25 GB
(1 row)
$ psql -U postgres -d cgms -c "SELECT pg_size_pretty(SUM(pg_indexes_size(table_schema||'.'||table_name) + pg_relation_size(table_schema||'.'||table_name))) as size from information_schema.tables"
size
--------
151 GB
(1 row)
$ sudo du -hsc /var/lib/pgsql/12/data
154G /var/lib/pgsql/12/data
154G total
Appreciate if someone can give some pointers.
Regards,
Karthik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karthik Jagadish (kjagadis) | 2022-11-15 15:40:58 | Re: Vacuumdb --force-index-cleanup option not available in postgres 12.9 |
| Previous Message | Justin Pryzby | 2022-11-15 15:32:32 | Re: Vacuumdb --force-index-cleanup option not available in postgres 12.9 |