Re: Worries about delayed-commit semantics

From: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Worries about delayed-commit semantics
Date: 2007-06-22 16:16:34
Message-ID: 467BF5E2.2070803@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-06-22 16:18:06 Re: tsearch in core patch
Previous Message Peter Eisentraut 2007-06-22 16:14:12 Re: GUC time unit spelling a bit inconsistent