From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Yan Cheng Cheok <yccheok(at)yahoo(dot)com> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Write Performance |
Date: | 2010-01-05 05:56:56 |
Message-ID: | 4B42D4A8.3080504@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yan Cheng Cheok wrote:
> Instead of sending 1000++ INSERT statements in one shot, which will requires my application to keep track on the INSERT statement.
>
> Is it possible that I can tell PostgreSQL,
>
> "OK. I am sending you INSERT statement. But do not perform any actual right operation. Only perform actual write operation when the pending statement had reached 1000"
>
You can turn off synchronous_commit to get something like that:
http://www.postgresql.org/docs/current/static/runtime-config-wal.html
This should make your single-record INSERT time drop dramatically. Note
that you'll be introducing a possibility of some data loss from the
latest insert(s) if the server crashes in this situation.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2010-01-05 06:03:39 | Re: PostgreSQL Write Performance |
Previous Message | Fujii Masao | 2010-01-05 05:17:24 | Re: timestams in the the pg_standby output |