pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michal Taborsky - Internet Mall <michal.taborsky@mall.cz>
To: Brad Nicholson <bnichols@ca.afilias.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Identifying bloated tables
Date: Mon, 28 Aug 2006 17:27:54 +0200
Message-ID: <44F30B7A.4020800@mall.cz> (raw)
In-Reply-To: <1156776499.10296.5.camel@dba5.int.libertyrms.com>
References: <44F30022.1000009@mall.cz>
	<1156776499.10296.5.camel@dba5.int.libertyrms.com>

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;



view thread (7+ messages)  latest in thread

Message-ID: <44F30B7A.4020800@mall.cz>
Permalink:  ../44F30B7A.4020800@mall.cz/
Also on:    postgresql.org/message-id/44F30B7A.4020800@mall.cz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: michal.taborsky@mall.cz, bnichols@ca.afilias.info
  Subject: Re: Identifying bloated tables
  In-Reply-To: <44F30B7A.4020800@mall.cz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox