pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Steve Crawford <scrawford@pinpointresearch.com>
To: Peter Kovacs <maxottovonstirlitz@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Do we need vacuuming when tables are regularly dropped?
Date: Mon, 29 Sep 2008 10:12:53 -0700
Message-ID: <48E10C95.2050207@pinpointresearch.com> (raw)
In-Reply-To: <b6e8f2e80809290533g2a7e09b1i110bb085ad75092e@mail.gmail.com>
References: <b6e8f2e80809290237p7685dbcfm9d5c886ba225b956@mail.gmail.com>
	<9815.1222690583@sss.pgh.pa.us>
	<b6e8f2e80809290533g2a7e09b1i110bb085ad75092e@mail.gmail.com>


>> 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




view thread (12+ messages)  latest in thread

Message-ID: <48E10C95.2050207@pinpointresearch.com>
Permalink:  ../48E10C95.2050207@pinpointresearch.com/
Also on:    postgresql.org/message-id/48E10C95.2050207@pinpointresearch.com

 · 

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-admin@postgresql.org
  Cc: scrawford@pinpointresearch.com, maxottovonstirlitz@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: Do we need vacuuming when tables are regularly dropped?
  In-Reply-To: <48E10C95.2050207@pinpointresearch.com>

* 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