X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 27F849FA4A7 for ; Fri, 30 Jun 2006 11:26:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 10743-09 for ; Fri, 30 Jun 2006 11:26:06 -0300 (ADT) X-Greylist: delayed 00:17:20.258895 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 06A909FA605 for ; Fri, 30 Jun 2006 11:26:05 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from wlittle.meridias.local (unknown [65.90.55.6]) by svr4.postgresql.org (Postfix) with ESMTP id 89C9B5AF040 for ; Fri, 30 Jun 2006 14:08:44 +0000 (GMT) Received: from wlittle.meridias.local (wlittle.meridias.local [127.0.0.1]) by wlittle.meridias.local (8.13.6/8.13.6) with ESMTP id k5UE8fwH023462 for ; Fri, 30 Jun 2006 08:08:41 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by wlittle.meridias.local (8.13.6/8.13.6/Submit) id k5UE8ePX023461 for pgsql-admin@postgresql.org; Fri, 30 Jun 2006 08:08:40 -0600 X-Authentication-Warning: wlittle.meridias.local: wjl set sender to warren.little@meridiascapital.com using -f From: Warren Little Organization: Meridias Capital To: pgsql-admin@postgresql.org Subject: auto vacuum doens't appear to be working Date: Fri, 30 Jun 2006 08:08:40 -0600 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606300808.40460.warren.little@meridiascapital.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/280 X-Sequence-Number: 22242 We have a bytea column where we store large attachments (ie pdf file). every so often (2 weekly) we replace the large a attachment (5-15mb) with a much smaller binary file (15k). when I run SELECT sum( relpages*8/1024 ) as MB FROM pg_class where relname != '' I get a value of 104995 which I interpret to mean I have 104GB of stored data in the database and this value has remained relatively static (+/- 1GB) over the past couple of weeks. We I to a df -h on the filesystem holding the database cluster I get a usage of 140GB. Again I interpret this to mean I have nearly 35GB of "uncleaned" data. Is this a case where I should be running the vacuum manually or is auto vacuum all that should be necessary to keep track and mark the updated tuple space ready for re-use. thanks -- Warren Little Chief Technology Officer Meridias Capital, Inc 1006 Atherton Dr Salt Lake City, UT 84123 ph. 866.369.7763