Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iZ9DL-00084f-Bn for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Nov 2019 07:55:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iZ9DJ-0006VD-Vk for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Nov 2019 07:55:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iZ9DJ-0006PA-JB for pgsql-hackers@lists.postgresql.org; Mon, 25 Nov 2019 07:55:17 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iZ9DG-0003f9-Tq for pgsql-hackers@postgresql.org; Mon, 25 Nov 2019 07:55:16 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 7E4FA5DF; Mon, 25 Nov 2019 02:55:13 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 25 Nov 2019 02:55:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=l+/yk4y7QygtgHV3KOXr6gRl1V/ Y+Lt8cOMRxO9SSS0=; b=fqVRwxF7nlJzrgMEXyADe+xb8W/FW4xyysgSR2ZFZ8R aGgDbwBNNoCiyfHUEDQuxbgLkHrmHd+QWg9f4mQOMdg6KQFoSgqDlcs5HiG0KRW8 7r8nnyjQNj+owmQ0xU27lPxOSFc/GgpNGSEXPBwXrYAXhsXP39SjxTlU6BJBIB3q V/dcIZioLcqihOi3qT2Tw2bt8/PCUeUiTqFgq5WFAEmcbvs0SQLHjcOgyUtLjhen KdyFIsS7vlbeTTPYP6JWRInnTI4YNNWw7KX5wThKZjBGpVGmYnuHvxz+KGNekHbQ 24RmMO2nK/Iy879nnvHhtWCtNKolJIQ9rBTHYAcxk3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=l+/yk4 y7QygtgHV3KOXr6gRl1V/Y+Lt8cOMRxO9SSS0=; b=DUuuDt80q8/v6JwQgD/P7e Tu8L8MgoW+DZP+cdAb7gXn/YhKWcf9iBrfKcGynInzNEjbmO6uUm7lJ3WzBJitgi lRAlbNuG33H+Y3g3YqrsUh0ETHOAj34TTbIyQDISgu3WxcSMFqmX/H4P9ARwzXYY VovqyrDAhTztU8UX6HDbPGxOkbt3m+2E7eVi+rhn4RBl2mR+P1OWp+e0QXRSleK2 TxhIDf/8TbTFBWqbawn/r9TEgwRmzPrZwb8krxT61IRjfZSw/hpR89N1BQZttBzU uzWMONtGHoI7UncyCtn3c9Ex0A7e65kCKanYMS8RhQM062Sr2QSe9a1W8WOsbexQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeitddghedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucfkphepudduuddruddtvddrudektddrudekheenucfrrghr rghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiienucevlh hushhtvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id C38998005A; Mon, 25 Nov 2019 02:55:11 -0500 (EST) Date: Mon, 25 Nov 2019 16:55:07 +0900 From: Michael Paquier To: Fabien COELHO Cc: Corey Huinker , pgsql-hackers@postgresql.org Subject: Re: Add A Glossary Message-ID: <20191125075507.GH99720@paquier.xyz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BXr400anF0jyguTS" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --BXr400anF0jyguTS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 09, 2019 at 09:19:16AM +0100, Fabien COELHO wrote: > On principle, I'm fine with having a glossary, i.e. word definitions, whi= ch > are expected to be rather stable in the long run. >=20 > I'm wondering whether the effort would not be made redundant by other > on-line effort such as wikipedia, wiktionary, stackoverflow, standards, > whatever. >=20 > When explaining something, the teacher I am usually provides some level of > example. This may or may not be appropriate there. That's exactly a good reason for being a reviewer here. You have quite some insight here. > I'd consider making SQL keywords uppercase. >=20 > Developing that is a significant undertaking. Do we have the available > energy? It seems like this could be a good idea, still the patch has been waiting on his author for more than two weeks now, so I have marked it as returned with feedback. -- Michael --BXr400anF0jyguTS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl3biNsACgkQnvQgOdby QH2sAw//R7fjp03QcFMwjcemn6ApanLuoyLLN61dnc/mm0NqHHy4DtHfHmc2lQ1u UuSIOS6Do0quIJkE20gHNPs0qCNfvhi0HAlfIZ6ufUVMgGTfwjaUCkXsu6MtU8zO h/zBGZMRtXsdTUgOzNCIobwmrVVRORugdHasH/EILUHoofV0kEr9UbR8rXOG5nmu DRCtlfBTm1jMVZ/ZUPWdTelb9kYDuJPkFwIOafbAVPbC8kypJBgjX0Mk1sDBEbpT cMmryC6keKCC3Fx1NOiJbvTY9TTTzsGXsWaV7NO8UWSpJbIWXs/SDUwWc5vdpKVl bbpp0Pm9goyBM7v83+5nggRUgPaWbGH+2avSIvMCY+x6gOGRjseSr2Os6W5fG9a7 Yem4OeAEffdsuWttuuexuOllk6D40NMO/FWkGIvMWgtH2aA0Ys3M5rnxakrL5OfS yZDPg9LTUk3mgHP57k44UctP2GaL15/pot/lIet/Ir7X44dssBSsp9f2B+uyzeyd Qnil0c0iL1Ha+C01PCAsOZa0uN7x30Cq9wQpw+9XD0U862Ppw/9bN3KpUoCTH5u+ UT+WuES7cFdfVO8OpZmzxByDoEgu66Vx6zzyjR+MBzgSAcVsT0C+tXMbKZsn9m3K +3kMMbhzt5isg0LGEMZIHEQDAaehshSlqhk6QNEfDfGC/kN7pOE= =T0JZ -----END PGP SIGNATURE----- --BXr400anF0jyguTS--