Date: Fri, 15 May 2020 13:26:19 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Erik Rijkers <er@xs4all.nl>, Laurenz Albe <laurenz.albe@cybertec.at>,
	Fabien COELHO <coelho@cri.ensmp.fr>,
	=?iso-8859-1?Q?J=FCrgen?= Purtz <juergen@purtz.de>,
	Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
	Corey Huinker <corey.huinker@gmail.com>,
	Roger Harkavy <rogerharkavy@gmail.com>,
	pgsql-hackers@postgresql.org, Michael Paquier <michael@paquier.xyz>
Subject: Re: Add A Glossary
Message-ID: <20200515172619.GA31053@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="HlL+5n6rz5pIUxbD"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200515010304.GN18456@telsasoft.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk


--HlL+5n6rz5pIUxbD
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Applied all these suggestions, and made a few additional very small
edits, and pushed -- better to ship what we have now in beta1, but
further edits are still possible.

Other possible terms to define, including those from the tweet I linked
to and a couple more:

archive
availability
backup
composite type
common table expression
data type
domain
dump
export
fault tolerance
GUC
high availability
hot standby
LSN
restore
secondary server (?)
snapshot
transactions per second

Anybody want to try their hand at a tentative definition?

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

--HlL+5n6rz5pIUxbD
Content-Type: text/x-diff; charset=iso-8859-1
Content-Disposition: attachment;
 filename="v3-0001-Review-of-the-glossary.patch"
Content-Transfer-Encoding: 8bit