Re: Asynchronous commit | Transaction loss at server crash

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Balkrishna Sharma <b_ki(at)hotmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Asynchronous commit | Transaction loss at server crash
Date: 2010-05-20 17:36:31
Message-ID: AANLkTil_HjG1Qn59ZZ6yc-rvm6nYTA1uTukIxo_iuhka@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, May 20, 2010 at 10:54 AM, Balkrishna Sharma <b_ki(at)hotmail(dot)com> wrote:
> I need to support several hundreds of concurrent update/inserts from an
> online form with pretty low latency (maybe couple of milliseconds at max).
> Think of a save to database at every 'tab-out' in an online form.

You can get nearly the same performance by using a RAID controller
with battery backed cache without the same danger of losing
transactions.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Sherry.CTR.Zhu 2010-05-20 17:56:46 installation on Sun Solaris for version 8.4
Previous Message Scott Marlowe 2010-05-20 17:35:39 Re: Asynchronous commit | Transaction loss at server crash