Re: [Fwd: Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum]

From: Ron St-Pierre <ron(dot)pgsql(at)shaw(dot)ca>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [Fwd: Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum]
Date: 2007-06-04 14:34:13
Message-ID: 466422E5.5040802@shaw.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andrew Sullivan wrote:
> On Fri, Jun 01, 2007 at 01:27:14PM -0700, Ron St-Pierre wrote:
>
>> imp=# select age(datfrozenxid) from pg_database where datname = 'imp';
>> age
>> ------------
>> 1571381411
>> (1 row)
>>
>> Time to start VACUUM FULL ANALYZE over the weekend.
>>
>
> I guess this comes too late, but you don't need VACUUM FULL for that.
Yes, I know that VACUUM FULL isn't required here, but because the
weekend is our slow time on the server I thought that I would perform a
full vacuum.
> VACUUM FULL _does not_ mean "vacuum everything"!
>
>
What do you mean by this? I wanted to do both a VACUUM ANALYZE and a
VACUUM FULL, so ran VACUUM FULL ANALYZE. Is there something odd about
VACUUM FULL, other than locking the table it's working on?
> A
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-06-04 14:35:38 Re: Numeric performances
Previous Message Rhys Stewart 2007-06-04 14:33:48 what to do when pg_cancel_backend() doesnt work?