Re: BUG #5322: Time to perform vacuums - Mailing list pgsql-bugs

From Eric Pailleau
Subject Re: BUG #5322: Time to perform vacuums
Date
Msg-id 4B7432D6.30809@numlog.fr
Whole thread Raw
In response to Re: BUG #5322: Time to perform vacuums  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Robert Haas a =E9crit :
> On Thu, Feb 11, 2010 at 11:25 AM, Robert Haas <robertmhaas@gmail.com> wro=
te:
>> I can see VACUUM making VACUUM FULL faster.  I don't think VACUUM FULL
>> should make VACUUM FULL ANALYZE faster.
>=20
> Err, let me correct myself.  A second VACUUM FULL should be faster
> than the first one.  But the two together I wouldn't expect to be
> faster than doing it all in one shot.
>=20
> ...Robert
Thank you Robert for your comments.

What seems to be a bug, could be a feature ?
May be performing a simple VACUUM first before a real VACUUM FULL
can be a solution to increase VACUUM FULL performances ?

(I mean VACUUM FULL could be done in 2 sequences , first a simple VACUUM th=
en a real VACUUM FULL).

The time difference is sometime 1 for 10 ! But it should be confirmed on ot=
her platforms and OS ...

Thanks anyway, I will stay with my three commands sequence, waiting for the=
 new CLUSTER command...

Postgreqlement .

--=20
Salutations - Best regards - mit freundlichen Gr=FCssen

pgsql-bugs by date:

Previous
From: Koichi Suzuki
Date:
Subject: Bug on pg_lesslog
Next
From: Robert Haas
Date:
Subject: Re: BUG #5314: Error in nested composite types in plpgsql.