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:35:39
Message-ID: AANLkTilevLpYSpa7e_6vJ_snoOeXnF3kaVqxmydjYF3G@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:
> 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

That's not exactly correct. Transactions that haven't been written to
WAL may be lost. This would be a small number of transactions.
Transactions written to the WAL but not to the main data store will
NOT be lost.

However, this may still not be an acceptable case for your usage.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2010-05-20 17:36:31 Re: Asynchronous commit | Transaction loss at server crash
Previous Message Alvaro Herrera 2010-05-20 17:20:04 Re: Clarification Needed: When does autovacuum daemon run?