From: Stéphane Schildknecht <stephane.schildknecht@postgresqlfr.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Vacuum goes worse
Date: Tue, 16 Oct 2007 17:26:15 +0200
Message-ID: <4714D817.30701@postgresqlfr.org> (raw)
In-Reply-To: <15640.1192544768@sss.pgh.pa.us>
References: <47147AD8.9010704@postgresqlfr.org>
<15640.1192544768@sss.pgh.pa.us>
Tom Lane a écrit :
> =?ISO-8859-1?Q?St=E9phane_Schildknecht?= <stephane.schildknecht@postgresqlfr.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: stephane.schildknecht@postgresqlfr.org, tgl@sss.pgh.pa.us
Subject: Re: Vacuum goes worse
In-Reply-To: <4714D817.30701@postgresqlfr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox