pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jürgen Purtz <juergen@purtz.de>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Corey Huinker <corey.huinker@gmail.com>
Cc: Roger Harkavy <rogerharkavy@gmail.com>
Cc: pgsql-hackers@postgresql.org, Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Michael Paquier <michael@paquier.xyz>
Subject: Re: Add A Glossary
Date: Sun, 5 Apr 2020 10:41:44 +0200
Message-ID: <79036db2-147d-bd9d-6fd2-587ccb2c5ea4@purtz.de> (raw)
In-Reply-To: <20200403205143.GA7961@alvherre.pgsql>
References: <20200403205143.GA7961@alvherre.pgsql>

a) Some rearrangements of the sequence of terms to meet alphabetical order.

b) <glossterm id="linkend-xxx">  --> <glossterm linkend="glossary-xxx">  
in two cases. Or should it be a <firstterm>?


Kind regards, Jürgen

Attachments:

glossfixes-2.patch (text/x-patch, 3.5K) download diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml index 8c6cb6e942..25762b7c3a 100644 --- a/doc/src/sgml/glossary.sgml +++ b/doc/src/sgml/glossary.sgml @@ -208,15 +208,6 @@ </glossdef> </glossentry> - <glossentry id="glossary-checkpointer"> - <glossterm>Checkpointer (process)</glossterm> - <glossdef> - <para> - A specialized process responsible for executing checkpoints. - </para> - </glossdef> - </glossentry> - <glossentry id="glossary-checkpoint"> <glossterm>Checkpoint</glossterm> <glossdef> @@ -244,6 +235,15 @@ </glossdef> </glossentry> + <glossentry id="glossary-checkpointer"> + <glossterm>Checkpointer (process)</glossterm> + <glossdef> + <para> + A specialized process responsible for executing checkpoints. + </para> + </glossdef> + </glossentry> + <glossentry> <glossterm>Class (archaic)</glossterm> <glosssee otherterm="glossary-relation" /> @@ -761,25 +761,6 @@ </glossdef> </glossentry> - <glossentry id="glossary-logger"> - <glossterm>Logger (process)</glossterm> - <glossdef> - <para> - If activated, the - <glossterm linkend="glossary-logger">Logger</glossterm> process - writes information about database events into the current - <glossterm linkend="glossary-log-file">log file</glossterm>. - When reaching certain time- or - volume-dependent criteria, a new log file is created. - Also called <firstterm>syslogger</firstterm>. - </para> - <para> - For more information, see - <xref linkend="runtime-config-logging"/>. - </para> - </glossdef> - </glossentry> - <glossentry id="glossary-log-record"> <glossterm>Log Record</glossterm> <glossdef> @@ -803,6 +784,25 @@ </glossdef> </glossentry> + <glossentry id="glossary-logger"> + <glossterm>Logger (process)</glossterm> + <glossdef> + <para> + If activated, the + <glossterm linkend="glossary-logger">Logger</glossterm> process + writes information about database events into the current + <glossterm linkend="glossary-log-file">log file</glossterm>. + When reaching certain time- or + volume-dependent criteria, a new log file is created. + Also called <firstterm>syslogger</firstterm>. + </para> + <para> + For more information, see + <xref linkend="runtime-config-logging"/>. + </para> + </glossdef> + </glossentry> + <glossentry> <glossterm>Master (server)</glossterm> <glosssee otherterm="glossary-primary-server" /> @@ -1651,6 +1651,11 @@ </glossdef> </glossentry> + <glossentry> + <glossterm>WAL</glossterm> + <glosssee otherterm="glossary-wal" /> + </glossentry> + <glossentry id="glossary-wal-archiver"> <glossterm>WAL Archiver (process)</glossterm> <glossdef> @@ -1696,11 +1701,6 @@ </glossdef> </glossentry> - <glossentry> - <glossterm>WAL</glossterm> - <glosssee otherterm="glossary-wal" /> - </glossentry> - <glossentry id="glossary-wal-record"> <glossterm>WAL Record</glossterm> <glossdef> @@ -1728,8 +1728,8 @@ <glossdef> <para> A process that writes <glossterm linkend="glossary-wal-record">WAL records</glossterm> - from <glossterm id="linkend-shared-memory">shared memory</glossterm> to - <glossterm id="linkend-wal-file">WAL files</glossterm>. + from <glossterm linkend="glossary-shared-memory">shared memory</glossterm> to + <glossterm linkend="glossary-wal-file">WAL files</glossterm>. </para> <para> For more information, see

view thread (97+ messages)  latest in thread

Message-ID: <79036db2-147d-bd9d-6fd2-587ccb2c5ea4@purtz.de>
Permalink:  ../79036db2-147d-bd9d-6fd2-587ccb2c5ea4@purtz.de/
Also on:    postgresql.org/message-id/79036db2-147d-bd9d-6fd2-587ccb2c5ea4@purtz.de

 ·  · 

reply

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, pryzby@telsasoft.com, corey.huinker@gmail.com, rogerharkavy@gmail.com, coelho@cri.ensmp.fr, michael@paquier.xyz
  Subject: Re: Add A Glossary
  In-Reply-To: <79036db2-147d-bd9d-6fd2-587ccb2c5ea4@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