Merlin Moncure wrote: > Postgres can handle multiple 1000 insert/sec but your hardware most > likely can't handle multiple 1000 transaction/sec if fsync is on. commit_delay or async commit should help a lot there. http://www.postgresql.org/docs/8.3/static/wal-async-commit.html http://www.postgresql.org/docs/8.3/static/runtime-config-wal.html Please do *not* turn fsync off unless you want to lose your data. > If you are bulk inserting 1000+ records/sec all day long, make sure > you have provisioned enough storage for this (that's 86M records/day), plus any index storage, room for dead tuples if you ever issue UPDATEs, etc. -- Craig Ringer -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
