Tom Lane wrote:
Tatsuo Ishii [EMAIL PROTECTED] writes:
Now that PostgreSQL 8.3 enables autovacuum by default, I think pgbench
should stop issuing vacuum in pgbench -i since an ordinary vacuum will
take very long time under autovacuum running. If there's no objection,
I will remove vacuum
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'd be inclined to leave it there, simply because you'll be changing
the conditions of the benchmark if you take it out. I have not noticed
any particular problems with it...
I wonder if autovacuum itself is going to add more
Hi,
Now that PostgreSQL 8.3 enables autovacuum by default, I think pgbench
should stop issuing vacuum in pgbench -i since an ordinary vacuum will
take very long time under autovacuum running. If there's no objection,
I will remove vacuum from pgbench.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Tatsuo Ishii [EMAIL PROTECTED] writes:
Now that PostgreSQL 8.3 enables autovacuum by default, I think pgbench
should stop issuing vacuum in pgbench -i since an ordinary vacuum will
take very long time under autovacuum running. If there's no objection,
I will remove vacuum from pgbench.
I'd be
On 9/25/07, Tom Lane [EMAIL PROTECTED] wrote:
I'd be inclined to leave it there, simply because you'll be changing
the conditions of the benchmark if you take it out. I have not noticed
any particular problems with it...
The only problem I faced is while executing custom scripts using
On Tue, 25 Sep 2007, Tatsuo Ishii wrote:
Now that PostgreSQL 8.3 enables autovacuum by default, I think pgbench
should stop issuing vacuum in pgbench -i since an ordinary vacuum will
take very long time under autovacuum running. If there's no objection,
I will remove vacuum from pgbench.
Just
On Tue, 2007-09-25 at 22:16 +0530, Pavan Deolasee wrote:
The only problem I faced is while executing custom scripts using
pgbench.
You either need to do the initialization (pgbench -i) or run with -n
option
(no vacuum). But I don't have any strong preference here.
Yes, I had that problem
