MIME-Version: 1.0
References: 
 <CADkLM=eP6HOeqDjn0FdXuGRusQu4oWH_LFsKjjafmhvWD=aSpQ@mail.gmail.com>
 <20200331180929.GH14618@telsasoft.com>
In-Reply-To: <20200331180929.GH14618@telsasoft.com>
From: Corey Huinker <corey.huinker@gmail.com>
Date: Tue, 31 Mar 2020 15:26:02 -0400
Message-ID: 
 <CADkLM=e0_0Vhks_AQnCq9broqZKR0BCv4WzUe4mHhODFW1cj8w@mail.gmail.com>
Subject: Re: Add A Glossary
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000008566d605a22b8a82"
Precedence: bulk

--0000000000008566d605a22b8a82
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 31, 2020 at 2:09 PM Justin Pryzby <pryzby@telsasoft.com> wrote:

> 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 ?
>

1. I asked some newer database people to come up with a list of terms that
they used.
2. I then added some more terms that seemed obvious given that first list.
3. That combined list was long on general database concepts and theory, and
short on administration concepts
4. Then J=C3=BCrgen suggested that we integrate his working list of terms, =
very
much focused on internals, so I did that.
5. Everything after that was applying suggested edits and new terms.


> Here's some ideas; I'm *not* suggesting to include all of everything, but
> hopefully start with a coherent, self-contained list.
>

I don't think this list will ever be complete. It will always be a work in
progress. I'd prefer to get the general structure of a glossary committed
in the short term, and we're free to follow up with edits that focus on the
wording.


>
> grep -roh '<firstterm>[^<]*' doc/src/ |sed 's/.*/\L&/' |sort |uniq -c
> |sort -nr |less
>
> Maybe also:
> object identifier
> operator classes
> operator family
> visibility map
>

Just so I can prioritize my work, which of these things, along with your
suggestions in previous emails, would you say is a barrier to considering
this ready for a committer?

--0000000000008566d605a22b8a82
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Mar 31, 2020 at 2:09 PM Justin Pr=
yzby &lt;<a href=3D"mailto:pryzby@telsasoft.com">pryzby@telsasoft.com</a>&g=
t; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">On Sun, Oct 13, 2019 at 04:52:05PM -0400, Corey Huinke=
r wrote:<br>
&gt; 1. It&#39;s obviously incomplete. There are more terms, a lot more, to=
 add.<br>
<br>
How did you come up with the initial list of terms ?<br></blockquote><div><=
br></div><div>1. I asked some newer database=C2=A0people to come up with a =
list of terms that they used.</div><div>2. I then added some more terms tha=
t seemed obvious given that first list.</div><div>3. That combined list was=
 long on general database concepts and theory, and short on administration =
concepts</div><div>4. Then=C2=A0J=C3=BCrgen suggested that we integrate his=
 working list of terms, very much focused on internals, so I did that.</div=
><div>5. Everything after that was applying suggested edits and new terms.<=
/div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>Here&#39;s some ideas; I&#39;m *not* suggesting to include all of everythi=
ng, but<br>
hopefully start with a coherent, self-contained list.<br></blockquote><div>=
<br></div><div>I don&#39;t think this list will ever be complete. It will a=
lways be a work in progress. I&#39;d prefer to get the general structure of=
 a glossary committed in the short term, and we&#39;re free to follow up wi=
th edits that focus on the wording.</div><div>=C2=A0<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
<br>
grep -roh &#39;&lt;firstterm&gt;[^&lt;]*&#39; doc/src/ |sed &#39;s/.*/\L&am=
p;/&#39; |sort |uniq -c |sort -nr |less<br>
<br>
Maybe also:<br>
object identifier<br>
operator classes<br>
operator family<br>
visibility map<br></blockquote><div><br></div><div>Just so I can prioritize=
 my work, which of these things, along with your suggestions in previous em=
ails, would you say is a barrier to considering this ready for a committer?=
=C2=A0</div></div></div>

--0000000000008566d605a22b8a82--