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 5913C528F4 for ; Wed, 17 Aug 2005 14:41:53 -0300 (ADT) 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 65806-09 for ; Wed, 17 Aug 2005 17:41:50 +0000 (GMT) Received: from hotmail.com (bay102-f41.bay102.hotmail.com [64.4.61.51]) by svr1.postgresql.org (Postfix) with ESMTP id B34BB5288A for ; Wed, 17 Aug 2005 14:41:49 -0300 (ADT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 17 Aug 2005 10:41:47 -0700 Message-ID: Received: from 64.4.61.202 by by102fd.bay102.hotmail.msn.com with HTTP; Wed, 17 Aug 2005 17:41:47 GMT X-Originating-IP: [64.4.61.202] X-Originating-Email: [bitsandbytes88@hotmail.com] X-Sender: bitsandbytes88@hotmail.com In-Reply-To: <1d219a6f05081709575c72f117@mail.gmail.com> From: "D Kavan" To: pgsql-admin@postgresql.org Subject: Re: vacuumdb -a -f Date: Wed, 17 Aug 2005 13:41:47 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 17 Aug 2005 17:41:47.0468 (UTC) FILETIME=[F0EDA8C0:01C5A352] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.872 required=5 tests=[AWL=-0.394, DNS_FROM_RFC_ABUSE=0.374, DNS_FROM_RFC_POST=1.376, FROM_ENDS_IN_NUMS=0.516, MSGID_FROM_MTA_HEADER=0] X-Spam-Level: * X-Archive-Number: 200508/226 X-Sequence-Number: 18545 CASE CLOSED! Thanks for the tip on the reindex script. That did the trick. It was one table in particuliar. ~DjK >From: Chris Hoover >To: Guido Barosio >CC: D Kavan , pgsql-admin@postgresql.org >Subject: Re: [ADMIN] vacuumdb -a -f >Date: Wed, 17 Aug 2005 12:57:16 -0400 > >You might want to try doing a reindexdb -a -e (reindexdb is in the >contrib directory of your pg source). The first time I ran this, I >gained back a significant amount of space. > >I now run a vacuumdb -v -f -a and then a reindexdb -a -e every weekend >to have PostgreSQL give back as much space as it can. I have ended up >doing this do to space and i/o constraints. > >Give the reindexdb script a try and see if you don't get your space back. > >HTH, > >Chris > >On 8/17/05, Guido Barosio wrote: > > How are you finding out the DB size? > > > > G.- > > > > > > > > On 8/17/05, D Kavan wrote: > > > Hi, > > > > > > Thanks for the tips. > > > > > > Unfortunatley for me, even after started doing vacuumdb -a 3 times a >day > > > and increasing fsm dramatically , the size of the database won't go >down > > > even 1 MB. It's stil at 5.6 GB, size after restore = 4 GB. I even >did a > > > stop/start instead of a re-load to make sure the settings took affect. > > Would > > > a reboot help? > > > > > > max_fsm_pages = 16000001 > > > max_fsm_relations = 1000000 > > > > > > shared_buffers = 65536 > > > work_mem = 32768 > > > maintenance work mem = 786432 > > > > > > checkpoint_segments = 18 > > > > > > > > > ##/etc/sysctl.conf > > > > > > nel.shmall = 524288 > > > #kernel.shmall = 2097152 > > > #kernel.shmmax = 2147483648 > > > #kernel.shmmax = 1073741824 > > > kernel.shmmax = 6979321856 > > > kernel.shmmni = 4096 > > > kernel.sem = 250 32000 100 128 > > > fs.file-max = 65536 > > > net.ipv4.ip_local_port_range = 1024 65000 > > > vm.overcommit_memory = 2 > > > > > > > > > ~DjK > > > > > > > > > > > > > > > > > > >From: Tom Lane > > > >To: "D Kavan" < bitsandbytes88@hotmail.com> > > > >CC: pgsql-admin@postgresql.org > > > >Subject: Re: [ADMIN] vacuumdb -a -f Date: Mon, 15 Aug 2005 21:31:01 >-0400 > > > > > > > >"D Kavan" writes: > > > > > Even though I run vacuumdb -a -f every night with no exceptions or > > > >problems, > > > > > my database size remains 5.6 GB. After I do a dump/restore, the >new > > > > > database size is 4.0 GB. How could that be possible? > > > > > > > >The extra 1.6GB probably represents the amount of junk you generate >in > > > >one day. So, forget the -f and instead do plain vacuums on a more > > > >frequent basis. Make sure your FSM settings are large enough, too. > > > > > > > > regards, tom lane > > > > > > > > > > > > ---------------------------(end of > > broadcast)--------------------------- > > > TIP 6: explain analyze is your friend > > > > > > > > > > > -- > > "Adopting the position that you are smarter than an automatic > > optimization algorithm is generally a good way to achieve less > > performance, not more" - Tom Lane.