| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add A Glossary |
| Date: | 2020-03-31 18:09:29 |
| Message-ID: | 20200331180929.GH14618@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Sun, Oct 13, 2019 at 04:52:05PM -0400, Corey Huinker wrote:
> 1. It's obviously incomplete. There are more terms, a lot more, to add.
How did you come up with the initial list of terms ?
Here's some ideas; I'm *not* suggesting to include all of everything, but
hopefully start with a coherent, self-contained list.
grep -roh '<firstterm>[^<]*' doc/src/ |sed 's/.*/\L&/' |sort |uniq -c |sort -nr |less
Maybe also:
object identifier
operator classes
operator family
visibility map
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2020-03-31 19:26:02 | Re: Add A Glossary |
| Previous Message | Justin Pryzby | 2020-03-31 18:07:40 | Re: Add A Glossary |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-03-31 18:10:34 | Re: backup manifests |
| Previous Message | Justin Pryzby | 2020-03-31 18:07:40 | Re: Add A Glossary |