From: Jürgen Purtz <juergen@purtz.de>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: 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>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Add A Glossary
Date: Wed, 17 Jun 2020 14:52:19 +0200
Message-ID: <292d6f42-e31c-bc73-6cfb-9083bc2c07fc@purtz.de> (raw)
In-Reply-To: <20200617000926.GA11060@alvherre.pgsql>
References: <20200617000926.GA11060@alvherre.pgsql>
On 17.06.20 02:09, Alvaro Herrera wrote:
> On 2020-Jun-09, Jürgen Purtz wrote:
>
>> 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."
> After sleeping on it a few more times, I don't oppose the idea of making
> "instance" be the running state and "database cluster" the on-disk stuff
> that supports the instance. Here's a patch that does things pretty much
> along the lines you suggested.
>
> I made small adjustments to "SQL objects":
>
> * SQL objects in schemas were said to have their names unique in the
> schema, but we failed to say anything about names of objects not in
> schemas and global objects. Added that.
>
> * Had example object types for global objects and objects not in
> schemas, but no examples for objects in schemas. Added that.
>
>
> Some programs whose output we could tweak per this:
> pg_ctl
>> pg_ctl is a utility to initialize, start, stop, or control a PostgreSQL server.
>> -D, --pgdata=DATADIR location of the database storage area
> to:
>> pg_ctl is a utility to initialize or control a PostgreSQL database cluster.
>> -D, --pgdata=DATADIR location of the database directory
> pg_basebackup:
>> pg_basebackup takes a base backup of a running PostgreSQL server.
> to:
>> pg_basebackup takes a base backup of a PostgreSQL instance.
+1, with two formal changes:
- Rearrangement of term "Data page" to meet alphabetical order.
- Add </glossdef> in one case to meet xml-well-formedness.
One last question: The definition of "Data directory" reads "... A
cluster's storage space comprises the data directory plus ..." and
'cluster' links to '"glossary-instance". Shouldn't it link to
"glossary-db-cluster"?
--
Jürgen Purtz
Attachments:0004-glossary.patch (text/x-patch, 1.9K) downloaddiff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgmlindex e29b55e5ac..0499f9044f 100644--- a/doc/src/sgml/glossary.sgml+++ b/doc/src/sgml/glossary.sgml@@ -413,6 +413,22 @@
</glossdef>
</glossentry>
+ <glossentry id="glossary-data-page">+ <glossterm>Data page</glossterm>+ <glossdef>+ <para>+ The basic structure used to store relation data.+ All pages are of the same size.+ Data pages are typically stored on disk, each in a specific file,+ and can be read to <glossterm linkend="glossary-shared-memory">shared buffers</glossterm>+ where they can be modified, becoming+ <firstterm>dirty</firstterm>. They become clean when written+ to disk. New pages, which initially exist in memory only, are also+ dirty until written.+ </para>+ </glossdef>+ </glossentry>+
<glossentry id="glossary-database">
<glossterm>Database</glossterm>
<glossdef>
@@ -441,6 +457,7 @@
<firstterm>cluster</firstterm> is also sometimes used to refer to an instance.
(Don't confuse this term with the SQL command <command>CLUSTER</command>.)
</para>
+ </glossdef>
</glossentry>
<glossentry>
@@ -448,22 +465,6 @@
<glosssee otherterm="glossary-instance" />
</glossentry>
- <glossentry id="glossary-data-page">- <glossterm>Data page</glossterm>- <glossdef>- <para>- The basic structure used to store relation data.- All pages are of the same size.- Data pages are typically stored on disk, each in a specific file,- and can be read to <glossterm linkend="glossary-shared-memory">shared buffers</glossterm>- where they can be modified, becoming- <firstterm>dirty</firstterm>. They become clean when written- to disk. New pages, which initially exist in memory only, are also- dirty until written.- </para>- </glossdef>- </glossentry>-
<glossentry id="glossary-datum">
<glossterm>Datum</glossterm>
<glossdef>
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, pgsql-docs@lists.postgresql.org
Subject: Re: Add A Glossary
In-Reply-To: <292d6f42-e31c-bc73-6cfb-9083bc2c07fc@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