Re: Vacuum full is slow

>>vacuum_cost_delay = 100
>>No idea how long will take normal vacuum. I ll try tonight when there is
>>not too much load.

That can really take the VACUUM a long time to complete, but you might want
to have it there as it will be good for performance by setting it a little
high in a high OLTP environment.

I will recommend setting it to 0 first and then you can start moving it high
as per your needs...

--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 3/19/07, Ruben Rubio <ruben(at)rentalia(dot)com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> >
> > You don't have vacuum_cost_delay set, do you? How long does normal
> > vacuum run?
>
> vacuum_cost_delay = 100
> No idea how long will take normal vacuum. I ll try tonight when there is
> not too much load.
>
> >
> > The manual suggests dropping all indexes before running vacuum full, and
> > recreating them afterwards. That's worth trying.
> >
>
> I ll try that also. Is there any way to do it? Do i have to delete /
> create each one manually?
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFF/pxLIo1XmbAXRboRAjR1AJ9V4kBDCd++HSmUm8+ZCLs2RY0xnACfZ7Mp
> uBC031TFhO2NGOihfWPAQQ8=
> =QCYi
> -----END PGP SIGNATURE-----
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>