X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 450E1DB20B for ; Fri, 28 Oct 2005 13:48: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 33972-01 for ; Fri, 28 Oct 2005 16:48:51 +0000 (GMT) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by svr1.postgresql.org (Postfix) with ESMTP id D789DDB222 for ; Fri, 28 Oct 2005 13:48:51 -0300 (ADT) Received: by xproxy.gmail.com with SMTP id i30so362287wxd for ; Fri, 28 Oct 2005 09:48:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Sg2jmEzoej9/kbCnlSQ6yiQwOR4HLHgvQT6yevGJOLG0rhw2elodIl74Suqt/kjwTmS+Rm9S0lsTYSshoc+Qgx4ot+clKsWuJ1wbgy6F48b8Kx0TClZE77E1nLgoz+DxPPVS2Z6LBY/KXRDZozQQoRSh9Z8tUQeCHpLDW6wwnLo= Received: by 10.70.109.20 with SMTP id h20mr312531wxc; Fri, 28 Oct 2005 09:48:51 -0700 (PDT) Received: by 10.70.105.15 with HTTP; Fri, 28 Oct 2005 09:48:51 -0700 (PDT) Message-ID: <72e966b00510280948h15fd8d56qc3aaca7840f2348d@mail.gmail.com> Date: Fri, 28 Oct 2005 10:48:51 -0600 From: Jan Peterson To: Csaba Nagy Subject: Re: How long it takes to vacuum a big table Cc: postgres performance list In-Reply-To: <1130512461.25950.20.camel@coppola.muc.ecircle.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1130512461.25950.20.camel@coppola.muc.ecircle.de> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.678 required=5 tests=[AWL=-0.654, RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 0.678 X-Spam-Level: X-Archive-Number: 200510/441 X-Sequence-Number: 15209 We've also experienced problems with VACUUM running for a long time.=20 A VACUUM on our pg_largeobject table, for example, can take over 24 hours to complete (pg_largeobject in our database has over 45million rows). With our other tables, we've been able to partition them (using inheritance) to keep any single table from getting "too large", but we've been unable to do that with pg_largeobject. Currently, we're experimenting with moving some of our bulk (large object) data outside of the database and storing it in the filesystem directly. I know that Hannu Krosing has developed some patches that allow concurrent VACUUMs to run more effectively. Unfortunately, these patches didn't get into 8.1 so far as I know. You can search the performance mailing list for more information. -jan- -- Jan L. Peterson