| From: | Michal Taborsky - Internet Mall <michal(dot)taborsky(at)mall(dot)cz> |
|---|---|
| To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Identifying bloated tables |
| Date: | 2006-08-28 15:27:54 |
| Message-ID: | 44F30B7A.4020800@mall.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Brad Nicholson napsal(a):
>> I just put together a view, which helps us in indentifying which
>> database tables are suffering from space bloat, ie. they take up much
> Are you sure you haven't reinvented the wheel? Have you checked out
> contrib/pgstattuple ?
Well, I wasn't aware of it, so I guess I did reinvent the wheel. I
Googled for a solution to this problem, but Googled poorly I suppose.
On the other hand, pgstattuple might be a bit difficult to use for
not-so-experienced users in answering the question "Which table should I
shrink?", as you have to first install it from contrib and then come up
with a select to pick the "worst" relations.
Anyway, if someone finds this view useful, good. If not, ignore it.
Bye.
--
Michal Táborský
IT operations chief
Internet Mall, a.s.
<http://www.MALL.cz>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-08-28 15:31:52 | Re: Identifying bloated tables |
| Previous Message | Tom Lane | 2006-08-28 15:13:55 | Re: Postgre SQL 7.1 cygwin performance issue. |