Re: High Frequency Inserts to Postgres Database vs Writing to a File - Mailing list pgsql-performance

From Craig Ringer
Subject Re: High Frequency Inserts to Postgres Database vs Writing to a File
Date
Msg-id 4AF22671.303@postnewspapers.com.au
Whole thread Raw
In response to Re: High Frequency Inserts to Postgres Database vs Writing to a File  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: High Frequency Inserts to Postgres Database vs Writing to a File  (Jay Manni <JManni@FireEye.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Dave Crooke
Date:
Subject: Followup: vacuum'ing toast
Next
From: Greg Smith
Date:
Subject: Re: Followup: vacuum'ing toast