Hi!
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Tom> Justin Clift <[EMAIL PROTECTED]> forwards:
>> The problem was that when we run the benchmark with the --fast option,
>> which basicly does a vacuum() between after each batch of updates,
>> postmaster started to fill up disk with log
Justin Clift <[EMAIL PROTECTED]> forwards:
> The problem was that when we run the benchmark with the --fast option,
> which basicly does a vacuum() between after each batch of updates,
> postmaster started to fill up disk with log files during one of the
> vacuum() runs and didn't stop until the d
Hi all,
The "MySQL Benchmark" page on the mysql.com website has benchmarks for
various databases :
http://www.mysql.com/information/benchmarks.html
In the PostgreSQL entry they aren't able to report an "accurate" result
for all things, as they haven't been able to get vacuum to work 100%
correc
