From: Jürgen Purtz <juergen@purtz.de>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Erik Rijkers <er@xs4all.nl>
To: Laurenz Albe <laurenz.albe@cybertec.at>
To: Fabien COELHO <coelho@cri.ensmp.fr>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Roger Harkavy <rogerharkavy@gmail.com>
Cc: pgsql-hackers@postgresql.org, Michael Paquier <michael@paquier.xyz>
Subject: Re: Add A Glossary
Date: Sun, 17 May 2020 08:15:48 +0200
Message-ID: <774bb48d-cd3d-17ee-77e9-937519bf9c6e@purtz.de> (raw)
In-Reply-To: <20200515000017.GA12687@alvherre.pgsql>
References: <20200515000017.GA12687@alvherre.pgsql>
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 removed "global SQL object" and made "SQL object" explain it.
+1., but see the (huge) different spellings in patch.
bloat: changed 'current row' to 'relevant row' because not only the
youngest one is relevant (non-bloat).
data type casts: Are you sure that they are global? In pg_cast
'relisshared' is 'false'.
--
Jürgen Purtz
Attachments:0002-glossfixes-purtz.patch (text/x-patch, 2.5K) downloaddiff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgmlindex 8bb1ea5d87..75f0dc9a8c 100644--- a/doc/src/sgml/glossary.sgml+++ b/doc/src/sgml/glossary.sgml@@ -179,7 +179,7 @@
<glossterm>Bloat</glossterm>
<glossdef>
<para>
- Space in data pages which does not contain current row versions,+ Space in data pages which does not contain relevant row versions,
such as unused (free) space or outdated row versions.
</para>
</glossdef>
@@ -1388,23 +1388,27 @@
<glossdef>
<para>
Any object that can be created with a <command>CREATE</command>
- command. Most objects are specific to one database, and are commonly- known as <firstterm>local objects</firstterm>.+ command. Most objects are specific to one schema within+ one database, and are commonly+ known as <firstterm>local SQL objects</firstterm>.+ </para>+ <para>+ Some of the SQL objects do not belong to a single schema but+ are known in all schemas of a database. Examples are+ <glossterm linkend="glossary-extension">extensions</glossterm> like+ <glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>, and+ <glossterm linkend="glossary-cast">data type casts</glossterm>.+ </para>+ <para>+ Some others even belong to the complete cluster and are+ known in all databases and all its schemas.
<glossterm linkend="glossary-role">Roles</glossterm>,
<glossterm linkend="glossary-tablespace">tablespaces</glossterm>,
replication origins, subscriptions for logical replication, and
- databases themselves are not local SQL objects since they exist- entirely outside of any specific database;- they are called <firstterm>global objects</firstterm>.+ all <firstterm>database names</firstterm> exist+ entirely outside of any specific database.+ They are called <firstterm>global SQL objects</firstterm>.
</para>
- <para>- Most local objects belong to a specific- <glossterm linkend="glossary-schema">schema</glossterm> in their containing database.- There also exist local objects that do not belong to schemas; some examples are- <glossterm linkend="glossary-extension">extensions</glossterm>,- <glossterm linkend="glossary-cast">data type casts</glossterm>, and- <glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>.- </para>
<para>
For more information, see
<xref linkend="manage-ag-overview"/>.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: juergen@purtz.de, alvherre@2ndquadrant.com, er@xs4all.nl, laurenz.albe@cybertec.at, coelho@cri.ensmp.fr, peter.eisentraut@2ndquadrant.com, corey.huinker@gmail.com, pryzby@telsasoft.com, rogerharkavy@gmail.com, michael@paquier.xyz
Subject: Re: Add A Glossary
In-Reply-To: <774bb48d-cd3d-17ee-77e9-937519bf9c6e@purtz.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox