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.92) (envelope-from ) id 1jIUGl-0003Lz-Bp for pgsql-hackers@arkaria.postgresql.org; Sun, 29 Mar 2020 09:30:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jIUGk-0008MJ-6u for pgsql-hackers@arkaria.postgresql.org; Sun, 29 Mar 2020 09:30:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jIUGj-0008MC-V3 for pgsql-hackers@lists.postgresql.org; Sun, 29 Mar 2020 09:30:13 +0000 Received: from mout.kundenserver.de ([217.72.192.74]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jIUGd-0001JW-38 for pgsql-hackers@postgresql.org; Sun, 29 Mar 2020 09:30:13 +0000 Received: from [192.168.178.43] ([77.185.76.93]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.145]) with ESMTPSA (Nemesis) id 1MtOOm-1j4nfS2OQo-00ut0w; Sun, 29 Mar 2020 11:29:52 +0200 Subject: Re: Add A Glossary To: Justin Pryzby Cc: Alvaro Herrera , Corey Huinker , Roger Harkavy , pgsql-hackers@postgresql.org, Fabien COELHO , Michael Paquier References: <20200320001122.GA19602@alvherre.pgsql> <20200320195841.GA13662@telsasoft.com> <64b49f34-eaf6-6de2-e951-0eb8d4afabc2@purtz.de> <20200327201200.GV20103@telsasoft.com> From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= Message-ID: Date: Sun, 29 Mar 2020 11:29:50 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20200327201200.GV20103@telsasoft.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Provags-ID: V03:K1:HuJs1CXV0+ZYpCSfcl+gQfVQqfkulJsWwRusAbCWk092Jw/WNv8 lpbx5nyaAxn3iEWxr7D2noOgdBj4Fyx59BZqTL0QOip/w88Rme7p8DHommhEGYAV+Qelisc fxYrsEmv/J7maJCXi6HNcGQwSgFwTeMB7RhFDk+JtO1EZzavIfJhI3HEWqRqtLYQlXBlzmA uEnzEktqHDdGXPCtjS3yA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:XZms3LuNCJY=:Blc1kcKYLTuCF6wxvImW6g 4hadQ4Nqg0DI2m6OHc+cVxCv6Pmupevx4K/VtnBwo2xKOgxpIar1iE5PwtVeypHVrzRfY1leC 0qXIhD4u/MmUx8yHATzgkl3RMFlNqbXXP7LhiIo629qRUOoIxEc+o0bDAkYGIfpOgxLdcv5mC zAcmfRzHJmku+taeErxYUgaaVJFn6db9V4vyJ+DWxQO1zMndz2Lm2ztuV2pj+0z08QNvI+V/X kLCiHP+UKCDLrwRk9M0OVcOx6KcOluBHi3Xl8/rpAVh/37hT8ORFZr8ZcMIsml5ImV496GASh 81qdCB8+PMnSipud+Lsq9RmRb/SJpBeNif4qlyR2BKeS98O7SuQZlLiOdMNrwtMApBUAH5y5Y evgj4e6+Wo8i448N1rYiUk2wUBDdpxCISsuMPUFZ7wsCjwCl6QiKUBrqstMb1zSqp/0YuX3YY 6BvN+NRg/naD9ebmPbDeF7RXiAfgzpR64hCkbeJn8NHKIj7b0TPfD83FDKT29ctvuJ/F80MfB Ybm50RUBjSS7lY+I38rMsMJ3EQCN+5x/zevSUvFEoeDQGWtiwe9DhIrNuIvX02y9VJK3IgBCH YQwBk5ISmE4OEZ5G8H+Res7OKfeK05DoDvOi5MEWGn1ZCNKQf8rmsbFHR9p7xeudJe/Hxuj81 cyrx6qSfXYkCFZaKz4eQWsJNZiIwM3oa1/tu45bbGXVl3n7hLFpgPQzQxG7oaZpSUAQ+QvX9d +V6n7SQq2nP6QYdvxIouSVQgu07iaz3XafrXBIfoglsq2hEgY89onNSsMlg/dzxFO561LDZa0 yG9a+JM9Vmo1mzxAJr2OiDu2oRvJ3uk0ST9sx+e0+KSiVTHG4mVbhzM7tv3Sgo9gdBsdEBZ List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 27.03.20 21:12, Justin Pryzby wrote: > On Fri, Mar 20, 2020 at 11:32:25PM +0100, Jürgen Purtz wrote: >>>> + Archiver >>> Can you change that to archiver process ? >> I prefer the short term without the addition of 'process' - concerning >> 'Archiver' as well as the other cases. But I'm not an native English >> speaker. > I didn't like it due to lack of context. > > What about "wal archiver" ? > > It occured to me when I read this. > https://www.postgresql.org/message-id/20200327.163007.128069746774242774.horikyota.ntt%40gmail.com > "WAL archiver" is ok for me. In the current documentation we have 2 places with "WAL archiver" and 4 with "archiver"-only (high-availability.sgml, monitoring.sgml). "backend process" is an exception to the other terms because the standalone term "backend" is sensibly used in diverse situations. Kind regards, Jürgen