| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
| Cc: | Michal Taborsky - Internet Mall <michal(dot)taborsky(at)mall(dot)cz>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Identifying bloated tables |
| Date: | 2006-08-28 15:31:52 |
| Message-ID: | 20060828153152.GH27526@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Brad Nicholson wrote:
> On Mon, 2006-08-28 at 16:39 +0200, Michal Taborsky - Internet Mall
> wrote:
> > I just put together a view, which helps us in indentifying which
> > database tables are suffering from space bloat, ie. they take up much
> > more space than they actually should. I though this might be useful for
> > some folk here, because the questions about bloat-related performance
> > degradation are quite common.
>
> Are you sure you haven't reinvented the wheel? Have you checked out
> contrib/pgstattuple ?
Actually, pgstattuple needs to scan the whole table, so I think having a
cheap workaround that gives approximate figures is a good idea anyway.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-08-28 15:49:28 | Re: Identifying bloated tables |
| Previous Message | Michal Taborsky - Internet Mall | 2006-08-28 15:27:54 | Re: Identifying bloated tables |