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

Re: COMMIT NOWAIT Performance Option

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: COMMIT NOWAIT Performance Option
Date: 2007-02-27 19:36:18
Message-ID: 36e682920702271136v72b4d29anbcadcfcef747b8b5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 2/27/07, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> It seriously narrows down the problem space to know that PostgreSQL does *not*
> allow data loss if it's physically possible to prevent it.

Seems like we're trying to protect users from themselves again.  This
is not a PostgreSQL database issue; it's a feature designed for
application developers and cases where there is the possibility of
acceptable data loss for certain types of operations or transactions.
We already have the capacity for loss when fsync is disabled; this is
just a more controlled feature.

Under Oracle, NOWAIT is an asynchronous commit... anyone that uses it
should understand that it's still not on-disk and that they can lose
it in the event of a failure.  That's what Oracle's docs even say.
It's just a risk vs. reward trade off.

-- 
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation            | fax: 732.331.1301
33 Wood Ave S, 3rd Floor            | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2007-02-27 19:56:16
Subject: Re: COMMIT NOWAIT Performance Option
Previous:From: Bruce MomjianDate: 2007-02-27 19:26:09
Subject: Re: conversion efforts (Re: SCMS question)

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