| From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | andy <andy(at)squeakycode(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg 8.3beta 2 restore db with autovacuum report |
| Date: | 2007-11-03 00:32:29 |
| Message-ID: | 1d4e0c10711021732y29372e56vc092af72031f48e2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro,
On 11/2/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Even though the restore times are very similar, I find it a bit
> disturbing that the "CREATE INDEX" is shown to be waiting. Was it just
> bad luck that the ps output shows it that way, or does it really wait
> for long?
I did the test again with the reference database I used a month ago.
My previous figures with 8.3devel of October 1st were:
- autovacuum off: 14m39
- autovacuum on, delay 20: 51m37
With 8.3devel of today, I have:
- autovacuum on, delay 20: 15m26
I can see (CREATE INDEX|ALTER TABLE) waiting from time to time in my
watch -n 1 but it disappears within 1 or 2 seconds so what Simon and
you did seems to work as expected AFAICS.
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | andy | 2007-11-03 01:46:08 | Re: pg 8.3beta 2 restore db with autovacuum report |
| Previous Message | Mark Wong | 2007-11-03 00:25:40 | Re: Test lab |