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

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

Re: [GENERAL] Great Bridge re-runs benchmark with MySQL "tuned"

Hi! > "Poul" == Poul L Christiansen <[EMAIL PROTECTED]> writes: Poul> It would be interesting to see how well PostgreSQL performed when it was Poul> tuned. Poul> Or has it allready been tuned? Yes, it was. According to Ned, they did run vacuum() on the tables before running the test and