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 56AFE32A204 for ; Thu, 30 Sep 2004 17:43:20 +0100 (BST) 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 64722-07 for ; Thu, 30 Sep 2004 16:43:17 +0000 (GMT) Received: from mail.metnet.navy.mil (jade.metnet.navy.mil [192.16.167.28]) by svr1.postgresql.org (Postfix) with SMTP id A584232A1FB for ; Thu, 30 Sep 2004 17:43:15 +0100 (BST) Received: (qmail 23498 invoked from network); 30 Sep 2004 16:43:13 -0000 Received: from unknown (HELO ?127.0.0.1?) (10.100.105.103) by mail.metnet.navy.mil with SMTP; 30 Sep 2004 16:43:13 -0000 Message-ID: <415C37A0.2080602@metnet.navy.mil> Date: Thu, 30 Sep 2004 09:43:12 -0700 From: Mike Darretta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Data Partition is Growing References: <415B49DA.4000503@metnet.navy.mil> <8082.1096506831@sss.pgh.pa.us> In-Reply-To: <8082.1096506831@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: 200409/289 X-Sequence-Number: 14992 Thanks. I'll investigate and let you know how things go.... Mike Tom Lane wrote: >Mike Darretta writes: > > >>I'm an application developer trying to understand a pg data partition >>issue. We are storing large objects (gifs) at a rate of about 1GIG /day. >>After about a week, most of the objects are recycled -- that is, an >>insert triggers a delete of a similar object. The postgres data >>partition, though, continues to grow, even though the objects are >>successfully deleted from the application *and* largeobject tables. >> >> > >You need to check your free-space-map settings --- it sounds like the >FSM is not large enough to keep track of all the free space in >pg_largeobject. > >If you do a "vacuum verbose" across the whole database, the tail end of >the (voluminous) printout will tell you something about where you need >to set the FSM parameters. > > regards, tom lane > > >