Re: Add A Glossary - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Add A Glossary
Date
Msg-id CADkLM=cQ1D4pA8GmBBftg7R+qQnJDHEgLvmxG4HBV8F6r4eiKg@mail.gmail.com
Whole thread Raw
In response to Re: Add A Glossary  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Add A Glossary  (Roger Harkavy <rogerharkavy@gmail.com>)
List pgsql-hackers
This latest version is an attempt at merging the work of Jürgen Purtz into what I had posted earlier. There was relatively little overlap in the terms we had chosen to define.

Each glossary definition now has a reference id (good idea Jürgen), the form of which is "glossary-term". So we can link to the glossary from outside if we so choose.

I encourage everyone to read the definitions, and suggest fixes to any inaccuracies or awkward phrasings. Mostly, though, I'm seeking feedback on the structure itself, and hoping to get that committed.


On Tue, Feb 11, 2020 at 11:22 PM Corey Huinker <corey.huinker@gmail.com> wrote:
It seems like this could be a good idea, still the patch has been
waiting on his author for more than two weeks now, so I have marked it
as returned with feedback.

In light of feedback, I enlisted the help of an actual technical writer (Roger Harkavy, CCed) and we eventually found the time to take a second pass at this.

Attached is a revised patch.
 
Attachment

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Improve search for missing parent downlinks in amcheck
Next
From: Alvaro Herrera
Date:
Subject: Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line