MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Fri, 03 Apr 2020 23:05:06 +0200
From: Erik Rijkers <er@xs4all.nl>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Corey Huinker
 <corey.huinker@gmail.com>, =?UTF-8?Q?J=C3=BCrgen_Purtz?= <juergen@purtz.de>,
 Roger Harkavy <rogerharkavy@gmail.com>, pgsql-hackers@postgresql.org, Fabien
 COELHO <coelho@cri.ensmp.fr>, Michael Paquier <michael@paquier.xyz>
Subject: Re: Add A Glossary
In-Reply-To: <20200403205143.GA7961@alvherre.pgsql>
References: <20200403205143.GA7961@alvherre.pgsql>
Message-ID: <010383c2fd391046e0baeab4b91cec43@xs4all.nl>
User-Agent: XS4ALL Webmail
Precedence: bulk

On 2020-04-03 22:51, Alvaro Herrera wrote:
> On 2020-Apr-03, Erik Rijkers wrote:
> 
>> On 2020-04-03 18:45, Alvaro Herrera wrote:
>> > Pushed now.  Many thanks to Corey who put the main thrust, and to Jürgen
>> > and Roger for the great help, and to Justin for the extensive review and
>> > Fabien for the initial discussion.
>> 
>> A few improvements:
> 
> Thanks!  That gives me the attached patch.
> 
>> Should also be a  lemmata in the glossary:
>> 
>> ACID
> 
> Agreed.  Wording suggestions welcome.

How about:

"
ACID

Atomicity, consistency, isolation, and durability. ACID is a set of 
properties of database transactions intended to guarantee validity even 
in the event of power failures, etc.
ACID is concerned with how the database recovers from such failures that 
might occur while processing a transaction.
"

>> 'archaic' should maybe be 'obsolete'. That seems to me to be an easier 
>> word
>> for non-native speakers.
> 
> Bummer ;-)

OK - we'll figure it out :)


> --
> Álvaro Herrera                https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services