| From: | Stefan Fercot <stefan(dot)fercot(at)dalibo(dot)com> |
|---|---|
| To: | Vikas Sharma <shavikas(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Table and Index bloating |
| Date: | 2017-11-27 09:17:30 |
| Message-ID: | cf40507d-5386-7dc1-cb1a-9a1a4ffa9f83@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
You can track that with some monitoring tools like check_pgactivity. The
queries can be found here :
https://github.com/ioguix/pgsql-bloat-estimation.
Tables :
https://github.com/ioguix/pgsql-bloat-estimation/blob/master/table/table_bloat.sql
Indexes :
https://github.com/ioguix/pgsql-bloat-estimation/blob/master/btree/btree_bloat.sql
Backups should also be part of your maintenance plan.
Vacuum/Analyse/Reindex is already a good basis.
Kind regards
On 11/27/2017 10:10 AM, Vikas Sharma wrote:
> Hi All,
>
> Could someone please provide the query/queries to find table and
> Index bloating in PgSql 9.3 onwards?
> and are there any other maintenance tasks inPgSql except vacuum & analyse.
>
> Regards
> Vikas
--
Stefan FERCOT
http://dalibo.com - http://dalibo.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakub Glapa | 2017-11-27 09:54:03 | ERROR: too many dynamic shared memory segments |
| Previous Message | Vikas Sharma | 2017-11-27 09:10:08 | Table and Index bloating |