Re: Asynchronous commit | Transaction loss at server crash

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(dot)marlowe(at)gmail(dot)com
> To: b_ki(at)hotmail(dot)com
> CC: pgsql-admin(at)postgresql(dot)org
>
> 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.
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)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.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4