From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pgbench -i order of vacuum |
Date: | 2012-07-20 00:05:36 |
Message-ID: | CAMkU=1y8-YpafmvQUChGqp85z+tXanGrMY37AHOcZoxgaW_vNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Is there a reason to vacuum the pgbench_* tables after the indexes on
them are built, rather than before?
Since the indexes are on fresh tables, they can't have anything that
needs to be cleaned.
I don't think the current order accomplishes anything, except to slow
down large initializations by ~25%.
The attached patch moves the vacuums up.
I also made -n skip the vacuums altogether. Since -n is allowed under
-i, it would be nice if it did something, and there is only one
intuitive thing for it to do. I don't know what the use case for is,
but I think I've heard grumbling about it before.
Cheers,
Jeff
Attachment | Content-Type | Size |
---|---|---|
pgbench_vacuum_order_v1.patch | application/octet-stream | 2.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-20 00:05:41 | Re: CHECK NO INHERIT syntax |
Previous Message | Tom Lane | 2012-07-20 00:02:42 | Re: 2GB limit for temp_file_limit on 32bit platform |