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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Worries about delayed-commit semantics


  • From: Richard Huxton <dev(at)archonet(dot)com>
  • To: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
  • Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Worries about delayed-commit semantics
  • Date: Fri, 22 Jun 2007 15:23:02 +0100
  • Message-id: <467BDB46(dot)1030901(at)archonet(dot)com>

Joshua D. Drake wrote:
Simon Riggs wrote:
On Fri, 2007-06-22 at 14:29 +0100, Gregory Stark wrote:
"Joshua D. Drake" <jd(at)commandprompt(dot)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?

I like "synchronous_commit = off", it even has a little girlfriend getting spin while being accurate :)

Or perhaps "sync_on_commit = off"?
Less girlfriend-speak perhaps:"no_sync_on_commit = on"

--
  Richard Huxton
  Archonet Ltd



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group