From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "Joshua D(dot) 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: | 2007-06-22 14:23:02 |
Message-ID: | 467BDB46.1030901@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-22 14:26:37 | Re: Worries about delayed-commit semantics |
Previous Message | Teodor Sigaev | 2007-06-22 14:12:36 | Re: tsearch in core patch |