From: Balkrishna Sharma <b_ki@hotmail.com>
To: pgsql-admin@postgresql.org
Subject: Asynchronous commit | Transaction loss at server crash
Date: Thu, 20 May 2010 12:54:56 -0400
Message-ID: <BAY149-w314344813824161D97E691F0E30@phx.gbl> (raw)
Hello,Couple of questions:1. For the 'Asynchronous commit' mode, I know that WAL transactions not flushed to permanent storage will be lost in event of a server crash. Is it possible to know what were the non-flushed transactions that were lost, in any shape/form/part ? I guess not, but wanted to confirm.
2. If above is true, then for my application 'Asynchronous commit' is not an option. In that case, how is it possible to increase the speed of 'Synchronous Commit' ? Can a SDD rather than HDD make a difference ? Can throwing RAM have an impact ? Is there some test somewhere of how much RAM will help to beef up the write process (for synch commit).
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.
Thanks,-Bala
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: b_ki@hotmail.com
Subject: Re: Asynchronous commit | Transaction loss at server crash
In-Reply-To: <BAY149-w314344813824161D97E691F0E30@phx.gbl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox