Re: Do we need vacuuming when tables are regularly dropped?

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: Peter Kovacs <maxottovonstirlitz(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Do we need vacuuming when tables are regularly dropped?
Date: 2008-09-29 17:12:53
Message-ID: 48E10C95.2050207@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


>> What it sounds like to me is that you're not vacuuming the system
>> catalogs, which are getting bloated with dead rows about all those
>> dropped tables.
>>
>
> Wow, great!
>
> It is not immediately clear from the documentation, but the VACUUM
> command also deals with the system catalogs as well, correct?
>
>

To expand on Tom's answer, rows in system tables are created not only
for tables but for each column in the table, rules, indexes, etc. You
can end up with a lot more row creation than you suspect. And temporary
tables bloat the system tables just like regular tables. We discovered
that cron scripts using temporary tables can cause very rapid
system-table blotage.

Cheers,
Steve

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2008-09-29 17:26:22 Re: Do we need vacuuming when tables are regularly dropped?
Previous Message Andrew Sullivan 2008-09-29 17:02:57 Re: turning of pg_xlog