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

From Bruce Momjian
Subject Re: Worries about delayed-commit semantics
Date
Msg-id 200706221443.l5MEh0P24230@momjian.us
Whole thread Raw
In response to Re: Worries about delayed-commit semantics  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Worries about delayed-commit semantics  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Worries about delayed-commit semantics  (PFC <lists@peufeu.com>)
List pgsql-hackers
Simon Riggs wrote:
> 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?

Yea, I like that too but I am now realizing that we are not really
deferring or delaying the "COMMIT" command but rather the recovery of
the commit.  GUC as full_commit_recovery?

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: GUC time unit spelling a bit inconsistent
Next
From: Bruce Momjian
Date:
Subject: Re: tsearch in core patch