Re: Worries about delayed-commit semantics - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Worries about delayed-commit semantics
Date
Msg-id 1182520293.9276.287.camel@silverbirch.site
Whole thread Raw
In response to Re: Worries about delayed-commit semantics  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Worries about delayed-commit semantics  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Worries about delayed-commit semantics  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Worries about delayed-commit semantics  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Fri, 2007-06-22 at 14:29 +0100, Gregory Stark wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> 
> > Tom Lane wrote:
> >
> >> untrustworthy disk hardware, for instance.  I'd much rather use names
> >> derived from "deferred commit" or "delayed commit" or some such.
> >
> > Honestly, I prefer these names as well as it seems directly related versus
> > transaction guarantee which sounds to be more like us saying, if we turn it off
> > our transactions are bogus.

That was the intention..., but name change accepted.

> Hm, another possibility: "synchronous_commit = off"

Ooo, I like that. Any other takers?

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: tsearch in core patch
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Worries about delayed-commit semantics