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 1jicNi-0001nk-W4 for pgsql-docs@arkaria.postgresql.org; Tue, 09 Jun 2020 11:25:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jicNh-0003jr-T1 for pgsql-docs@arkaria.postgresql.org; Tue, 09 Jun 2020 11:25:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jicNh-0003jh-NX; Tue, 09 Jun 2020 11:25:25 +0000 Received: from mout.kundenserver.de ([212.227.126.131]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jicNe-0004tH-Sf; Tue, 09 Jun 2020 11:25:24 +0000 Received: from [192.168.178.43] ([77.185.39.9]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.129]) with ESMTPSA (Nemesis) id 1Movrq-1jA4Rr32ic-00qToC; Tue, 09 Jun 2020 13:25:05 +0200 Subject: Re: Add A Glossary To: Alvaro Herrera Cc: Erik Rijkers , Laurenz Albe , Fabien COELHO , Peter Eisentraut , Corey Huinker , Justin Pryzby , Roger Harkavy , pgsql-hackers@postgresql.org, Michael Paquier , Pg Docs References: <20200517152851.GA31376@alvherre.pgsql> From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= Message-ID: Date: Tue, 9 Jun 2020 13:25:04 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200517152851.GA31376@alvherre.pgsql> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Provags-ID: V03:K1:mko+ZHYOLtrF+KKGXQ0OWNdq5n5jr8EUz79EITXR3cAx7rgtB/J M0EcJb61G189mDYMy9KVYsKHUmJHHIggbHdiHqr3KgvpLDLitcm/Y7GeX6DmCSq8sIZX5TQ EyB4M7bBoYsuGKSS5peXKW7Z6X+NX/RfELeRhzd4EZVhbbxjEElYxYx1DPucwalRWbpGJ90 wzKHeC2zkxgi+iech+/qw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:sEbTnrhmRB8=:8LYOSOyKd9yGawQJGbk5wT HwCeONbiFhVutONIu0OMVb4Coi4m9Ky3cTfA5BvxWQlSUXk8nsBoeq9P3Uepv/S9RK42F+OiM mri3Rj7uUV9X4noc8p5x8c0UJb9dCdbPEd1eO6NSh16S68hZKlgbfvvg9cqH/eIX/BPRlITAX hNYdoyhNQNM6hu2+OB+ncvTWLCgY2hIOtYImwv+4sNHz7B6erE4VPIN+hzWguj/pXc9U13qFA VNfBmRqxjciWKXPyjUBK3+jwS62aFwP1KiIWQuSJ/XEU7Z4Oyk5H/0Trfn951YQl0U7DEhtSU YJjKisrTxOWNm3afgL/Qm+7SV22Uka1zSpLMTWs7a8C7C9rqfYlivayTzA5K7+gQXi+nWWMH1 zaUxe8UllEUhQXyMukNXfXI/GJf6thR+aknAkwrb2LMyto5i27Ket9X1P2CJHdZJupyMm7QiT Ln4Dhp7wYWngsSvEAVv2Y/EjizDSkdR/1r2olFVLYYizba6UdDSq5oPC5jUs8e7DQEEDQMAkb I8GEoSDuODi+IylKT1mdqUmLpuONEEZEfsQBXd5cRO/+q6opR9XIFXxRCirz8Lxm/SAf+4VfV 8JF+4dtait+QIsGbTkNzF0xJ3+BGAsQS9Kk4e676IUO+q7E/IGhvsZcHmGoECQRCWbX+lHVvw 22XTKtyvVVuBDblVlKKGRO4Cg+n1j5tholPfMPEThoH2b4xULHkGsS/vvyGwhg/3Ze51Ml9tI gAK41A9W3IAmXAMnbqJrjbgLqtWFpjV6xuOi8wi+E0wLdKXOr0LGFVr+0xtHvd/Fyf8OSCn8m 2c/1N+Vnuv44QNn2tUi/c1nzYNJd5wAGDDVG44BLbB2FYpxqLQ7DLsl8YtgTvTbbSmO2OYV List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 17.05.20 17:28, Alvaro Herrera wrote: > I think the terms under discussion are just > > * cluster > * instance > * server Despite the short period of its existence the glossary achieved some importance, see: https://www.postgresql.org/message-id/b8e12875ebec9e6d3107df5fa1129e1e%40postgrespro.ru . We have to be careful with publications. It's not acceptable that we change definitions from release to release. Therefore IMO we should mark or even ignore such terms for which we cannot reach consensus. Can you agree to the following definitions? If no, we can alternatively formulate for each of them: "Under discussion - currently not defined". My proposals are inspired by chapter 2.2 Concepts: "Tables are grouped into databases, and a collection of databases managed by a single PostgreSQL server instance constitutes a database cluster." - "Database" (No change to existing definition): "A named collection of SQL objects." - "Database Cluster", "Cluster" (New definition and rearrangements of some sentences): "A collection of related databases, and their common static and dynamic meta-data. This term is sometimes used to refer to an instance. (Don't confuse the term CLUSTER with the SQL command CLUSTER.)" - "Data Directory" (Replaced 'instance' by 'cluster'): "The base directory on the filesystem of a server that contains all data files and subdirectories associated with a cluster (with the exception of tablespaces). The environment variable PGDATA is commonly used to refer to the data directory. A cluster's storage space comprises the data directory plus any additional tablespaces. For more information, see Section 68.1." - "Database Server", "Instance" (Major changes): "A group of backend and auxiliary processes that communicate using a common shared memory area. One postmaster process manages the instance; one instance manages exactly one cluster with all its databases. Many instances can run on the same server as long as their TCP ports do not conflict. The instance handles all key features of a DBMS: read and write access to files and shared memory, assurance of the ACID properties, connections to client processes, privilege verification, crash recovery, replication, etc." - "Server" (No change to existing definition): "A computer on which PostgreSQL instances run. The term server denotes real hardware, a container, or a virtual machine. This term is sometimes used to refer to an instance or to a host." - "Host" (No change to existing definition): "A computer that communicates with other computers over a network. This is sometimes used as a synonym for server. It is also used to refer to a computer where client processes run." -- Jürgen Purtz