Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jKhwh-0002Rj-W3 for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2020 12:30:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jKhwg-0006Ry-JZ for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2020 12:30:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jKhwg-0006Rr-CM for pgsql-hackers@lists.postgresql.org; Sat, 04 Apr 2020 12:30:42 +0000 Received: from mout.kundenserver.de ([212.227.126.187]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jKhwa-0006dV-NZ for pgsql-hackers@postgresql.org; Sat, 04 Apr 2020 12:30:41 +0000 Received: from [192.168.178.43] ([77.180.28.93]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.129]) with ESMTPSA (Nemesis) id 1MMoKq-1jdKiZ1dJM-00IiVZ; Sat, 04 Apr 2020 14:30:15 +0200 From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= Subject: Re: Add A Glossary To: Laurenz Albe , Justin Pryzby , Alvaro Herrera Cc: Erik Rijkers , Corey Huinker , Roger Harkavy , pgsql-hackers@postgresql.org, Fabien COELHO , Michael Paquier References: <7b9b469e804777ac9df4d37716db935e@xs4all.nl> <20200403205143.GA7961@alvherre.pgsql> <20200403210120.GA12283@telsasoft.com> <686e65ba48801791816771e993ff5eebe571fac9.camel@cybertec.at> Message-ID: <19521520-719c-5c47-d196-3385617d5c03@purtz.de> Date: Sat, 4 Apr 2020 14:30:14 +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: <686e65ba48801791816771e993ff5eebe571fac9.camel@cybertec.at> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:gpIu9zLiF7aT7uewmB8WHoulrMmS/K8p9TJK8ZfZWl3eidzyLsn xsN5rrg9o85usb6DJJca9S/Hn07sSZe6uyQgk+jGFdiv3WXmbGNiIH5wsZA/c3VNPgjyEjv lykLmzeTkRk8ld07MMMmgX5neaH7J5kQxUvJbv3jL7RoSZ+iF94+gf5tbJzJQeKcCKFCacK g8qf5avDsMMxECtx1vCTg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:v+r9+9ifDXs=:B4qhyvj2PkPEez4WbYBrdY mIZ031FmjPqMxTI/uVeKiOa38QSACpjpk75RdZsoOJRqV3XWQYvsz3yYGXKbQK/LZCVWm7ILh 2wwh3+a4kOEXOZrGEH4omfTzZLT913Tx85LQQgmF5pS2MOMb2hv67dI+iLTmm5Be+k7Ggmhga l9TymVzIoDzjEwb2Fa5T3ee+Rje+F14j46mahyInhfEfRS6UsYcwIm0AlH1nQCcq1Soa4Aoe8 JuS5aQhcKgV9JrHoT8yj01125/+Rx4SZI3SdorPh2w3+NKRMAQPM1AnsohcwE1G7QTdLSA3fn 38rEPKgSBvB6ghdSSyW95X5mBY4kUwzRhJ7iG07ZkTb+aaWjVwiW/OOH4aVf09V5pkrmxed5S grgGRoZWKwo9UkhJViccmiZ4oZ/xRP0B2PbP8Y7D3Mf5e+vW56dVD4Ruo8dac7OVd2bV06cpZ iKBcKkEGJGKzF1RH90lTx2MfK+9DINWZT5EyMB6MqBd4ulgAJ81j/QxJjsgKOhUrpTxp/KfjD S3WkoaG6mT3YO9Z79T2rQ2D1zhKXKOUavLMYNJtWDieTVxUnR1AV0wAX8V3kmuoAPIoT9poiV fvusAgJaaZ7yUBmgv5QgBT1KzaIcffNNGa72htNwOJBCA+pugRfzM93nDz58osJCnmCKE5kAm U9jlen6iiLxvMajk+MQZ4+am2DtB5tDMdJKfwW9uIYHhRHwuMMAkb/cFiE5lxvAWEYiEylu1a RiCqqURkrifbly8c2ZLg4D5NjpXy2c3bC6sRWdAqonKvgv3KcomqYuMja9hipU0tbpAzxG3x+ rmrJR5Zs8M3SIQWTyP21dh4kPuLIz94jOazNaDUC55OTZH94jHREq35z+DSV6ZCiTJ/VQaO List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > - Server: is that really our definition? > I thought that "server" is what the glossary defines as "instance", and > the thing called "server" in the glossary should really be called "host". > > Maybe I am too Unix-centered. > > Many people I know use "instance" synonymous to "cluster". Currently our documentation uses 'server', 'database server', 'host', 'instance', ...  in an indifferent way. Similar problem with database/cluster. Now we have the chance to come to a conclusion about preferred terms an their exact meaning. Definitions in the glossary shall be the guideline, the documentation itself can adopt these terms over time. Here is my point of view. We have distinguishable things: (1) (virtual) hardware (2) an abstract structure of several object types, which models a management system for data (3) a group of closely related processes. They implement the internal 'business logic' or 'work flow' of (2). (4) abstract data, which fits into (2) (5) a physical representation of (4). Mainly and long lasting on disc, but - partly - mirrored in RAM. (6) client processes, which connect to (3) IMO for (1) the two terms 'server' and 'host' both have their justification, depending on the context. There are historical terms ('server-side', 'foreign server', 'client/server architecture', 'host' or 'host name' for IP-specification, 'host variable') which cannot be changed. Therefor we shall accept both with identical definition and use them as synonyms. Independent from this, there are many paragraphs in the documentation, where they are used in a misleading sense ('server crash', '... started the server', 'database server'). They should be changed over time. For me, (3) is an 'instance' and (5) is a 'cluster'. There is a 1:1 relation between the two, because one 'instance' controls exactly one 'cluster'. But the 'instance' consists of processes and memory whereas the 'cluster' of databases which resides (mainly) on disc. Concerning (6) we are not interested in any hardware-question. We are only interested in the processes, which connect to backend processes. We should only define the term "Client process". Kind regards, Jürgen