On 3/23/06, Tom Lane <[EMAIL PROTECTED]> wrote: > > amarokcollection=# select relname, pg_relation_size(oid) FROM > > pg_class ORDER BY 2 DESC LIMIT 20; > > relname | pg_relation_size > > ---------------------------------+------------------ > > pg_attribute_relid_attnam_index | 2881069056 > > pg_class_relname_nsp_index | 1185890304 > > That's in a different database --- evidently, the one where a *whole* > lotta temp tables have been created and dropped. If you haven't been > doing any vacuuming then system catalog bloat is to be expected.
Oh sure enough it is.. I'm glad I copied the prompt. :) So it's by design that these now bloated index won't shrink if let unvacuumed? I didn't expect to hit something like that. Okay, so long as it wasn't a bug. I've reindexed the system tables now. The database is now 6mb on disk.. a big improvement from 6gb. :) Thanks. ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq