Re: Add A Glossary - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Add A Glossary
Date
Msg-id CADkLM=eP6+QgeaPQfvoLB+DzXEg798AbnMq-fc9TzHCgFzHtJQ@mail.gmail.com
Whole thread Raw
In response to Re: Add A Glossary  (Jürgen Purtz <juergen@purtz.de>)
Responses Re: Add A Glossary  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers


On Thu, Apr 2, 2020 at 8:44 AM Jürgen Purtz <juergen@purtz.de> wrote:
+1 and many thanks to Alvaros edits.


I did some of the grunt work Alvaro alluded to in v6, and the results are attached and they build, which means there are no invalid links.

Notes:
* no definition wordings were changed
* added a linkend to all remaining glossterms that do not immediately follow a glossentry
* renamed id glossary-temporary-tables to glossary-temporary-table
* temporarily re-added an id for glossary-row as we have many references to that. unsure if we should use the term Tuple in all those places or say Row while linking to glossary-tuple, or something else
* temporarily re-added an id for glossary-segment, glossary-wal-segment, glossary-analytic-function, as those were also referenced and will need similar decisions made
* added a stub entry for glossary-unique-index, unsure if it should have a definition on it's own, or we split it into unique and index.
* I noticed several cases where a glossterm is used twice in a definition, but didn't de-term them
* I'm curious about how we should tag a term when using it in its own definition. same as anywhere else?


 
Attachment

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: backup manifests
Next
From: Robert Haas
Date:
Subject: Re: backup manifests