Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 3787F2E2EE5 for ; Sun, 13 Jan 2008 22:05:13 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 07606-08-2 for ; Sun, 13 Jan 2008 22:05:01 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 520232E2D9A for ; Sun, 13 Jan 2008 22:05:06 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id m0E24ocX017199; Sun, 13 Jan 2008 21:04:50 -0500 (EST) To: d.wall@computer.org cc: pgsql-admin@postgresql.org Subject: Re: large objects & space usage In-reply-to: <478AB3B4.1090600@computer.org> References: <200801131301.04468.kevin@kevinkempterllc.com> <8811.1200258265@sss.pgh.pa.us> <478AB3B4.1090600@computer.org> Comments: In-reply-to David Wall message dated "Sun, 13 Jan 2008 16:58:28 -0800" Date: Sun, 13 Jan 2008 21:04:50 -0500 Message-ID: <17198.1200276290@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/143 X-Sequence-Number: 27917 David Wall writes: > Does the psql command 'vacuum;' by itself automatically vacuum > pg_largeobject along with all of tables in the database? Yes, if it's issued by a superuser or the database owner. However, that won't help much if pg_largeobject has become bloated by a lot of no-longer-wanted BLOBs. After deleting those, you'll probably need VACUUM FULL or CLUSTER or some such if you want to reclaim the disk space. Plain VACUUM usually isn't very successful at shortening a table file. regards, tom lane