Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 08BFE632B3D for ; Wed, 31 Mar 2010 01:33:08 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 58511-06 for ; Wed, 31 Mar 2010 04:32:57 +0000 (UTC) X-Greylist: delayed 00:12:09.397502 by SQLgrey-1.7.6 Received: from mail.illumen.com (unknown [64.207.29.137]) by mail.postgresql.org (Postfix) with ESMTP id 662AA632815 for ; Wed, 31 Mar 2010 01:32:57 -0300 (ADT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAD089.890CC1DF" Subject: Reclaiming space from a toast table Date: Tue, 30 Mar 2010 22:20:46 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Reclaiming space from a toast table thread-index: AcrQiYeDwkDqGIj8TV6vJudYomdFUg== From: "Benjamin Krajmalnik" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.102 tagged_above=-10 required=5 tests=BAYES_50=0.001, HTML_MESSAGE=0.001, RDNS_NONE=0.1 X-Spam-Level: X-Archive-Number: 201003/264 X-Sequence-Number: 34063 This is a multi-part message in MIME format. ------_=_NextPart_001_01CAD089.890CC1DF Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We recently added a text field to a table, and ended up dropping it and moving it to a separate related table for performance reasons. Previously, the toast table size was negligible, but now it is over 250MB. I have tried performing a vacuum full against the table (this is an inherited table), but it did not appear to reclaim the space. Is there any way to reclaim the space other than a dump/restore of the tables? ------_=_NextPart_001_01CAD089.890CC1DF Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We recently added a text field to a table, and = ended up dropping it and moving it to a separate related table for performance = reasons.

Previously, the toast table size was negligible, = but now it is over 250MB.

I have tried performing a vacuum full against the = table (this is an inherited table), but it did not appear to reclaim the = space.

Is there any way to reclaim the space other than a dump/restore of the tables?

------_=_NextPart_001_01CAD089.890CC1DF--