On Thu, Feb 3, 2011 at 7:08 PM, Vinubalaji Gopal <vinubal...@gmail.com> wrote: > already does this. I looked at the WAL parameters and the new async > commit but not sure if I am looking at the right place. Say i have 10 > clients connecting and each client is inserting a record. I want to >
You want the async commit. If you can detect and re-execute "lost" transactions, it gives you the best of everything: defer disk I/O and transaction boundaries are honored so you never have inconsistent data after crash recovery. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
