From: | "Eric Pailleau" <eric(at)numlog(dot)fr> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #5322: Time to perform vacuums |
Date: | 2010-02-10 13:56:00 |
Message-ID: | 201002101356.o1ADu0fO032494@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5322
Logged by: Eric Pailleau
Email address: eric(at)numlog(dot)fr
PostgreSQL version: 8.2.3
Operating system: linux debian
Description: Time to perform vacuums
Details:
Hello,
I really don't know if it can be a bug or not,
but when I do a 'VACCUM FULL ANALYZE VERBOSE',
it can take a very long time (expecially on large tables), while doing this
sequence of 3 commands is
quite quicker (on my system at least).
VACCUM VERBOSE
then
VACCUM FULL VERBOSE
then
VACCUM FULL ANALYZE VERBOSE
I mean adding the 'three commands' times is less than the time for the
direct 'VACCUM FULL ANALYZE VERBOSE'.
Does the fact of doing a 'simple' VACUUM first, make
other VACCUM more quick ? Does it finally does the same ? Is it only
coincidence due to system load ?
Thanks for your comments about this...
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-02-10 15:06:19 | Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze |
Previous Message | Oleg Serov | 2010-02-10 13:40:23 | Re: BUG #5314: Error in nested composite types in plpgsql. |