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 1jaD97-0004dA-Fs for pgsql-hackers@arkaria.postgresql.org; Sun, 17 May 2020 06:51:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jaD95-0004Rj-Dv for pgsql-hackers@arkaria.postgresql.org; Sun, 17 May 2020 06:51:35 +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 1jaD95-0004Rc-0U for pgsql-hackers@lists.postgresql.org; Sun, 17 May 2020 06:51:35 +0000 Received: from mail-qv1-xf43.google.com ([2607:f8b0:4864:20::f43]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jaD91-0002v8-OR for pgsql-hackers@postgresql.org; Sun, 17 May 2020 06:51:34 +0000 Received: by mail-qv1-xf43.google.com with SMTP id p4so3206281qvr.10 for ; Sat, 16 May 2020 23:51:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=gT9RbNDMov1J1kZiOrcTV1Q6xx0U+Gs8OeNTFTk2ezk=; b=Fa2a9VLEOdazgpU+Fpwhwb19ukxaoRBWAsqv7xYoC59JFt+xCFHKzdUf4lQIKyWF2E PkjIflFcXdxUQa0NAJO2UuLVatOjqvojX7AH2inqgzLLRb/PEUVf12hgQ8S3B2bafGZE 72cab0ts/4TaSaaZsQ2tW/ua/4DpcVgaklAAKEdxkWebWhpDm1KSrxY6LwhR5aSaQhx4 BVPgo0khHXZ9dRb5xXjd0DKCIRj4U+f6PoaZ9XtRdQlX+UX3fz+Rt/LDCNyGo7Orwv1/ cCpH+mkUH1GqQpPUkjt3rJizfvldVPH5X1KgTeRe8FBQSLlUF/coLoEhpn5Ux7l1poyP Pg9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=gT9RbNDMov1J1kZiOrcTV1Q6xx0U+Gs8OeNTFTk2ezk=; b=rgzPUM4Qp7o0tPI78N4BI7JE9c/dDXI0PEr/et+hJxR2a2LC+t5qlCXAaj5CE2TInc owxqDz862hr8lojD+9h5XmK4C9JxHCpOojmVWPBAL6nOStLFGuHwiRCLyYBVlpGO/OG4 MfkGjxq4ldDypMeqZ5lIpefFjGLj7JgES86Jyo+AZR289cYXNqUrfRtfAsq6lz9EoEK2 uEZR0oLZ8t4noGkw0aXDQLls1se/mc6jUNhWt/fI2mRTh855DqA2cWAPJLs56+uv3CE0 DoaxOIqzUNVtWvvtI9oFnVtqzTK8xLDjIyak3yubURRR/ptqgXcoq0TSFrdp/U0wEXhS KG7Q== X-Gm-Message-State: AOAM530Q01p9bAFMcuuUQdk7Gj4yE2IEsWGhLwn66QD0TexSpImHsepO tW3zXpDVuE1EcutaGC0Sd2yUgA== X-Google-Smtp-Source: ABdhPJx/rO4y92SVO76G7SmGXRn3QnEtqy+2alyzawtAuCSo96GLOpFGkpUxBt8aWLlbfYzErqUrLA== X-Received: by 2002:a0c:db03:: with SMTP id d3mr10860613qvk.80.1589698289740; Sat, 16 May 2020 23:51:29 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id m13sm6663573qtm.12.2020.05.16.23.51.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 16 May 2020 23:51:28 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 954D730070F; Sun, 17 May 2020 02:51:26 -0400 (-04) Date: Sun, 17 May 2020 02:51:26 -0400 From: Alvaro Herrera To: =?iso-8859-1?Q?J=FCrgen?= Purtz Cc: Erik Rijkers , Laurenz Albe , Fabien COELHO , Peter Eisentraut , Corey Huinker , Justin Pryzby , Roger Harkavy , pgsql-hackers@postgresql.org, Michael Paquier Subject: Re: Add A Glossary Message-ID: <20200517065126.GA20730@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <774bb48d-cd3d-17ee-77e9-937519bf9c6e@purtz.de> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-May-17, Jürgen Purtz wrote: > On 15.05.20 02:00, Alvaro Herrera wrote: > > Thanks everybody. I have compiled together all the suggestions and the > > result is in the attached patch. Some of it is of my own devising. > > > > * I changed "instance", and made "cluster" be mostly a synonym of that. > In my understanding, "instance" and "cluster" should be different things, > not only synonyms. "instance" can be the term for permanently fluctuating > objects (processes and RAM) and "cluster" can denote the more static objects > (directories and files). What do you think? If you agree, I would create a > patch. I don't think that's the general understanding of those terms. For all I know, they *are* synonyms, and there's no specific term for "the fluctuating objects" as you call them. The instance is either running (in which case there are processes and RAM) or it isn't. > > * I removed "global SQL object" and made "SQL object" explain it. > +1., but see the (huge) different spellings in patch. This seems a misunderstanding of what "local" means. Any object that exists in a database is local, regardless of whether it exists in a schema or not. "Extensions" is one type of object that does not belong in a schema. "Foreign data wrapper" is another type of object that does not belong in a schema. Same with data type casts. They are *not* global objects. > bloat: changed 'current row' to 'relevant row' because not only the youngest > one is relevant (non-bloat). Hm. TBH I'm not sure of this term at all. I think we sometimes use the term "bloat" to talk about the dead rows only, ignoring the free space. > data type casts: Are you sure that they are global? In pg_cast 'relisshared' > is 'false'. I'm not saying they're global. I'm saying they're outside schemas. Maybe this definition needs more rewording, if this bit is unclear. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services