From: | M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com> |
---|---|
To: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Cc: | Neeraj Gupta G <neeraj(dot)g(dot)gupta(at)ericsson(dot)com>, Atul Parashar <atul(dot)parashar(at)ericsson(dot)com>, Shishir Singh <shishir(dot)singh(at)globallogic(dot)com>, Ankit Sharma <ankit(dot)sharma10(at)globallogic(dot)com> |
Subject: | Autovacuum not functioning for large tables but it is working for few other small tables. |
Date: | 2020-12-16 11:54:55 |
Message-ID: | AM6PR0702MB3783F4CFF71E3FD27E9C9AC0AEC50@AM6PR0702MB3783.eurprd07.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
Hi all,
We have facing some discrepancy in Postgresql database related to the autovacuum functionality.
By default autovacuum was enable on Postgres which is used to remove the dead tuples from the database.
We have observed autovaccum cleaning dead rows from table_A but same was not functioning correctly for table_B which have a large size(100+GB) in comparision to table_A.
All the threshold level requirements for autovacuum was meet and there are about Million’s of dead tuples but autovacuum was unable to clear them, which cause performance issue on production server.
Is autovacuum not working against large sized tables or Is there any parameters which need to set to make autovacuum functioning?
Any suggestions?
Regards
Tarkeshwar
From | Date | Subject | |
---|---|---|---|
Next Message | M Tarkeshwar Rao | 2020-12-16 11:55:47 | RE: Autovacuum not functioning for large tables but it is working for few other small tables. |
Previous Message | Atul Kumar | 2020-12-16 09:35:26 | protect data of postgres database |
From | Date | Subject | |
---|---|---|---|
Next Message | M Tarkeshwar Rao | 2020-12-16 11:55:47 | RE: Autovacuum not functioning for large tables but it is working for few other small tables. |
Previous Message | Sebastijan Wieser | 2020-12-14 15:01:48 | Performance issues with composite types (partitioned table) |