Re: tuning postgresql writes to disk - Mailing list pgsql-general

From Vick Khera
Subject Re: tuning postgresql writes to disk
Date
Msg-id AANLkTi=sjSBpKwDLPpsAZ0oFDu2GPaSAjSvWio15gxuC@mail.gmail.com
Whole thread Raw
In response to tuning postgresql writes to disk  (Vinubalaji Gopal <vinubalaji@gmail.com>)
Responses Re: tuning postgresql writes to disk  (Vinubalaji Gopal <vinubalaji@gmail.com>)
List pgsql-general
On Thu, Feb 3, 2011 at 7:08 PM, Vinubalaji Gopal <vinubalaji@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.

pgsql-general by date:

Previous
From: Andre Lopes
Date:
Subject: Slow Inserts, two different scenarios.
Next
From: Vick Khera
Date:
Subject: Re: Directing Partitioned Table Searches