Re: [Fwd: MySQL Benchmark page - Problem with vacuum() in PostgreSQL]

Justin Clift <justin@postgresql.org> 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 disk was full.

See
http://www.ca.postgresql.org/mhonarc/pgsql-patches/2001-06/msg00061.html

            regards, tom lane