From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Any reasons to not move pgstattuple to core? |
Date: | 2013-10-03 21:37:02 |
Message-ID: | CAL_0b1voMF83Fgnn7PjbyvzF0obS08-ORr17qbwkdL+v0uNzkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
In my practice I quite often face the problem of bloated tables. I
usually use pgstattuple to perform investigations. I also create a
tool that uses UPDATEs based way to smoothly remove bloat
(https://github.com/grayhemp/pgtoolkit) and it partially depends on
pgstatuple too. To be more precise it gets much more effective with
pgstattuple.
Sometimes its installation leads to a headache, because it requires an
approve from security and admins, it also a problem when I have a
read-only access or no access to the database at all (eg. when
consulting somebody by IM or phone). I think I am not the only person
who faced these nuances.
According to this I would like to know if it is possible to move
pgstattuple to core? And if it is I would like to request this
feature.
Thank you.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-10-03 22:22:31 | Re: record identical operator |
Previous Message | Alvaro Herrera | 2013-10-03 21:31:02 | Re: GIN improvements part 1: additional information |