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.
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-07-20 00:05:41|
|Subject: Re: CHECK NO INHERIT syntax|
|Previous:||From: Tom Lane||Date: 2012-07-20 00:02:42|
|Subject: Re: 2GB limit for temp_file_limit on 32bit platform|