Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 95BA32E2D65 for ; Sun, 13 Jan 2008 20:58:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 26746-01 for ; Sun, 13 Jan 2008 20:58:28 -0400 (AST) Received: from mail2.yozons.com (mail2.yozons.com [63.251.168.97]) by postgresql.org (Postfix) with ESMTP id C7AF62E2E00 for ; Sun, 13 Jan 2008 20:58:27 -0400 (AST) Received: from [192.168.1.2] (pool-71-164-18-27.sttlwa.fios.verizon.net [71.164.18.27]) (authenticated bits=0) by mail2.yozons.com (8.12.10/8.12.10) with ESMTP id m0E0wPlG006917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 13 Jan 2008 16:58:26 -0800 Message-ID: <478AB3B4.1090600@computer.org> Date: Sun, 13 Jan 2008 16:58:28 -0800 From: David Wall Reply-To: d.wall@computer.org User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: large objects & space usage References: <200801131301.04468.kevin@kevinkempterllc.com> <8811.1200258265@sss.pgh.pa.us> In-Reply-To: <8811.1200258265@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/142 X-Sequence-Number: 27916 > If there are no other tables storing large objects in the database, > dropping and reloading the whole database is probably the simplest > solution. Otherwise they're going to need to make sure the unwanted > LOs have been cleaned out (see contrib/vacuumlo) and then do a VACUUM > FULL or similar on pg_largeobject. > Does the psql command 'vacuum;' by itself automatically vacuum pg_largeobject along with all of tables in the database? David