Re: tuning postgresql writes to disk

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: tuning postgresql writes to disk
Date: 2011-02-07 14:23:45
Message-ID: AANLkTi=sjSBpKwDLPpsAZ0oFDu2GPaSAjSvWio15gxuC@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Feb 3, 2011 at 7:08 PM, Vinubalaji Gopal <vinubalaji(at)gmail(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vick Khera 2011-02-07 14:32:38 Re: Directing Partitioned Table Searches
Previous Message Andre Lopes 2011-02-07 14:12:59 Slow Inserts, two different scenarios.