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

From Florian G. Pflug
Subject Re: Worries about delayed-commit semantics
Date
Msg-id 467BF5E2.2070803@phlo.org
Whole thread Raw
In response to Re: Worries about delayed-commit semantics  (Richard Huxton <dev@archonet.com>)
List pgsql-hackers
Richard Huxton wrote:
> Bruce Momjian wrote:
>> Tom Lane wrote:
>>> What's wrong with synchronous_commit?  It's accurate and simple.
>>
>> That is fine too.
> 
> My concern would be that it can be read two ways:
> 1. When you commit, sync (something or other - unspecified)
> 2. Synchronise commits (to each other? to something else?)*
> 
> It's obvious to people on the -hackers list what we're talking about, 
> but is it so clear to a newbie, perhaps non-English speaker?
> 
> * I can see people thinking this means something like "commit_delay".

OTOH, the concept of synchronous vs. asynchronous (function) calls
should be pretty well-known among database programmers and administrators.
And (at least to me), this is really what this is about - the commit
happens asynchronously, at the convenience of the database, and not
the instant that I requested it.

greetings, Florian Pflug



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: GUC time unit spelling a bit inconsistent
Next
From: Alvaro Herrera
Date:
Subject: Re: tsearch in core patch