Re: Any reasons to not move pgstattuple to core?
От | Robert Haas |
---|---|
Тема | Re: Any reasons to not move pgstattuple to core? |
Дата | |
Msg-id | CA+TgmoYkK5AOfa1HxeYOpCczch5mUnAQhian7Wm2cBH1P=aVog@mail.gmail.com обсуждение исходный текст |
Ответ на | Any reasons to not move pgstattuple to core? (Sergey Konoplev <gray.ru@gmail.com>) |
Ответы |
Re: Any reasons to not move pgstattuple to core?
|
Список | pgsql-hackers |
On Thu, Oct 3, 2013 at 5:37 PM, Sergey Konoplev <gray.ru@gmail.com> wrote: > 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. Well, this is a general problem with any extension - somebody might want it on a system on which the admin is unable or unwilling to install it. But we can't put every possible extension in core. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: