Skip site navigation (1) Skip section navigation (2)

Re: Async Commit, v21 (now: v22)

From: Florian Weimer <fweimer(at)bfk(dot)de>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Async Commit, v21 (now: v22)
Date: 2007-07-24 09:46:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
* Simon Riggs:

>> I think fsync=off also endagers metadata, while synchronous_commit=off
>> should be perfectly safe as far as the metadata is concerned.
>> Wouldn't this be worth mentioning as well?
> Well, I think "wider data loss" covers it for me, but I don't have a
> problem with people wanting to detail the various problems that can
> occur. 

To be honest, I'm mostly concerned with the "synchronous_commit=off
does not wedge the whole database" part of that statement.  For me as
a user, this is a crucial piece of information, and I don't like it
when such information is merely implied.

Florian Weimer                <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH
Kriegsstra├če 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

In response to

pgsql-patches by date

Next:From: Magnus HaganderDate: 2007-07-24 11:03:59
Subject: plperl warnings on win32
Previous:From: Simon RiggsDate: 2007-07-24 09:44:03
Subject: Re: Async Commit, v21 (now: v22)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group