Re: Asynchronous commit | Transaction loss at server crash - Mailing list pgsql-admin

From Balkrishna Sharma
Subject Re: Asynchronous commit | Transaction loss at server crash
Date
Msg-id BAY149-w7E2586A2E044680536BD8F0E30@phx.gbl
Whole thread Raw
In response to Asynchronous commit | Transaction loss at server crash  (Balkrishna Sharma <b_ki@hotmail.com>)
Responses Re: Asynchronous commit | Transaction loss at server crash
List pgsql-admin
Good suggestion. Thanks.
What's your take on SSD ? I read somewhere that moving the WAL to SSD helps as well.

> Date: Thu, 20 May 2010 11:36:31 -0600
> Subject: Re: [ADMIN] Asynchronous commit | Transaction loss at server crash
> From: scott.marlowe@gmail.com
> To: b_ki@hotmail.com
> CC: pgsql-admin@postgresql.org
>
> On Thu, May 20, 2010 at 10:54 AM, Balkrishna Sharma <b_ki@hotmail.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.
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin


The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy.

pgsql-admin by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: installation on Sun Solaris for version 8.4
Next
From: Scott Marlowe
Date:
Subject: Re: Asynchronous commit | Transaction loss at server crash