Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D99759FB897 for ; Fri, 25 May 2007 08:10:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 05745-02 for ; Fri, 25 May 2007 08:10:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from wp045.webpack.hosteurope.de (wp045.webpack.hosteurope.de [80.237.132.52]) by postgresql.org (Postfix) with ESMTP id C209B9FB7EE for ; Fri, 25 May 2007 08:10:10 -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 1HrXgP-00039K-Ir; Fri, 25 May 2007 13:10:09 +0200 Message-ID: <4656C411.8010509@bastian-voigt.de> Date: Fri, 25 May 2007 13:10:09 +0200 From: Bastian Voigt User-Agent: Thunderbird 2.0.0.0 (X11/20070502) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: 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> In-Reply-To: <4656C1C7.3000003@archonet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de; post@bastian-voigt.de; 1180091410; 2a351ea7; X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.449 tagged_above=0 required=5 tests=AWL=-0.087, BAYES_40=-0.185, RCVD_IN_NJABL_PROXY=0.721 X-Spam-Level: X-Archive-Number: 200705/494 X-Sequence-Number: 24884 Richard Huxton wrote: > > I was about to say that you can tune pg_autovacuum, but I just checked > your original post and you're running 8.0.x - not sure about that one. The system catalog pg_autovacuum which allows finetuning autovacuum at table level was introduced in 8.1 :-( > You'll have to check the documentation for that version to see if you > can either: > 1. exclude that table from pg_autovacuum > 2. increase pg_autovacuum's sensitivity (1) seems to be impossible (correct me if I'm wrong..), so maybe I'll go for (2) ... > If not, and this table is the most active, it might be simpler just to > run your own vacuum-ing from a cron job. Well, it is one of the most active, but there are others. pg_autovacuum seems to do a very good job, apart from this one table... -- Bastian Voigt Neumünstersche Straße 4 20251 Hamburg telefon +49 - 40 - 67957171 mobil +49 - 179 - 4826359