Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id A14689FB325 for ; Tue, 16 Oct 2007 12:26:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 54486-03-2 for ; Tue, 16 Oct 2007 12:26:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from dalibo-free-72.custom.lost-oasis.net (unknown [212.85.154.72]) by postgresql.org (Postfix) with ESMTP id F1BA39FB36E for ; Tue, 16 Oct 2007 12:26:23 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by dalibo-free-72.custom.lost-oasis.net (Postfix) with ESMTP id A367A578072; Tue, 16 Oct 2007 17:26:22 +0200 (CEST) Received: from dalibo-free-72.custom.lost-oasis.net ([127.0.0.1]) by localhost (pyrrha.dalibo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjFUGt2nQyq5; Tue, 16 Oct 2007 17:26:22 +0200 (CEST) Received: by dalibo-free-72.custom.lost-oasis.net (Postfix, from userid 1011) id 8AF6D578076; Tue, 16 Oct 2007 17:26:22 +0200 (CEST) Received: from [192.168.1.100] (unknown [81.56.152.169]) by dalibo-free-72.custom.lost-oasis.net (Postfix) with ESMTP id BB89A578072; Tue, 16 Oct 2007 17:26:19 +0200 (CEST) Message-ID: <4714D817.30701@postgresqlfr.org> Date: Tue, 16 Oct 2007 17:26:15 +0200 From: =?ISO-8859-1?Q?St=E9phane_Schildknecht?= User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: Tom Lane CC: "pgsql-performance@postgresql.org" Subject: Re: Vacuum goes worse References: <47147AD8.9010704@postgresqlfr.org> <15640.1192544768@sss.pgh.pa.us> In-Reply-To: <15640.1192544768@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/186 X-Sequence-Number: 27208 Tom Lane a écrit : > =?ISO-8859-1?Q?St=E9phane_Schildknecht?= writes: > >> For some times, we have a vacuuming process on a specific table that >> goes slower and slower. In fact, it took some 3 minutes a month ago, and >> now it take almost 20 minutes. But, if one day it take so many time, it >> is possible that on the day after it will only take 4 minutes... >> > > >> I know the table in concern had 450000 tuples two months ago and now has >> more than 700000 tuples in it. >> > > The real question is how often do rows get updated? I suspect you > probably need to vacuum this table more than once a day. > > To be honest, I suspect it too. But, I have been told by people using that database they can't do vacuum more frequently than once in a day as it increases the time to achieve concurrent operations. That's also why they don't want to hear about autovacuum. And finally that's why I'm looking for everything I can monitor to obtain information to convince them they're wrong and I'm right ;-) That's also why I am so disappointed vacuum doesn't give me these 4 hints lines. Regards, -- Stéphane SCHILDKNECHT Président de PostgreSQLFr http://www.postgresqlfr.org