On Fri, Jul 20, 2012 at 12:26 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Jeff Janes jeff.ja...@gmail.com writes:
On Fri, Jul 20, 2012 at 7:57 AM, Amit Kapila amit.kap...@huawei.com wrote:
The command it executes is vacuum analyze .., so it will do analyze also
on table which means
it will collect
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Jeff Janes
Sent: Friday, July 20, 2012 5:36 AM
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,
On Fri, Jul 20, 2012 at 7:57 AM, Amit Kapila amit.kap...@huawei.com wrote:
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Jeff Janes
Sent: Friday, July 20, 2012 5:36 AM
Is there a reason to vacuum the pgbench_* tables after the indexes on
Jeff Janes jeff.ja...@gmail.com writes:
On Fri, Jul 20, 2012 at 7:57 AM, Amit Kapila amit.kap...@huawei.com wrote:
The command it executes is vacuum analyze .., so it will do analyze also
on table which means
it will collect stats corresponding to table and index.
Are there stats collected
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
