Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D4FAE9FB701 for ; Fri, 25 May 2007 11:06:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 83367-03 for ; Fri, 25 May 2007 11:06:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from wp045.webpack.hosteurope.de (wp045.webpack.hosteurope.de [80.237.132.52]) by postgresql.org (Postfix) with ESMTP id 295CC9FB6D3 for ; Fri, 25 May 2007 11:06:16 -0300 (ADT) Received: from d088150.adsl.hansenet.de ([80.171.88.150] helo=[192.168.1.44]); authenticated by wp045.webpack.hosteurope.de running ExIM using esmtpa id 1HraQo-0001yz-KH; Fri, 25 May 2007 16:06:14 +0200 Message-ID: <4656ED56.608@bastian-voigt.de> Date: Fri, 25 May 2007 16:06:14 +0200 From: Bastian Voigt User-Agent: Thunderbird 2.0.0.0 (X11/20070502) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: My quick and dirty "solution" (Re: Performance Problem with Vacuum of bytea table (PG 8.0.13)) References: <46569E6A.2060509@bastian-voigt.de> <4656BB5E.3000109@archonet.com> <4656BEF1.4050609@bastian-voigt.de> <4656C1C7.3000003@archonet.com> <4656C411.8010509@bastian-voigt.de> <4656CDC2.6030106@archonet.com> <4656D6EC.5060506@bastian-voigt.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de; post@bastian-voigt.de; 1180101975; f1773e7f; X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.609 tagged_above=0 required=5 tests=AWL=-0.113, BAYES_50=0.001, RCVD_IN_NJABL_PROXY=0.721 X-Spam-Level: X-Archive-Number: 200705/505 X-Sequence-Number: 24895 Kristo Kaiv wrote: > you should first cluster the table on primary key. > The table is probably already bloated from the 3 hr delay it had before. > First > CLUSTER "primary key index name" ON group_fin_account_tst; > Then > vacuum it every 3 minutes. > NB! clustering takes an access exclusive lock on table Kristo, thanks a bunch!! This was the solution... The cluster operation took about 60sec, and after it was done the vacuum finished in only 10sec. or so, with no noticeable performance bottleneck. Now vacuum is running every 2-3 minutes and makes no problems. Hhhh, now I can look forward to a laid-back weekend.. Richard, Kristo, Alvaro, thanks 1000 times for responding so quickly :-) -- Bastian Voigt Neumünstersche Straße 4 20251 Hamburg telefon +49 - 40 - 67957171 mobil +49 - 179 - 4826359