X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9FECB5E46CB for ; Fri, 13 Aug 2004 16:02:28 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 53402-03 for ; Fri, 13 Aug 2004 19:02:19 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5F7875E3639 for ; Fri, 13 Aug 2004 16:02:19 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i7DJ2JHK025926; Fri, 13 Aug 2004 15:02:19 -0400 (EDT) To: "Thomas Madsen" Cc: pgsql-admin@postgresql.org Subject: Re: TOAST tables keeps growing! In-reply-to: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local> References: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local> Comments: In-reply-to "Thomas Madsen" message dated "Thu, 12 Aug 2004 16:46:02 +0200" Date: Fri, 13 Aug 2004 15:02:19 -0400 Message-ID: <25925.1092423739@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/113 X-Sequence-Number: 14508 "Thomas Madsen" writes: > What can I do to reclaim the wasted TOAST diskspace? vacuum full might help. > Can I find and eliminate the lost TOAST tuples somehow? Well, one thing to ask is whether it's the toast *table* that's bloating, or the *index* on the toast table. (VACUUM VERBOSE would help you find out.) If it's the table, then more frequent plain vacuums and/or increasing FSM should fix it. If the index is growing while the table stays about the same, you could try periodic REINDEXes, but the only real solution is to move up to PG 7.4. regards, tom lane