public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jürgen Purtz <[email protected]>
To: [email protected]
Cc: Corey Huinker <[email protected]>
Cc: Liudmila Mantrova <[email protected]>
Subject: Re: Shrinking SVG (Again)
Date: Sat, 15 Feb 2020 09:19:32 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>


> So now we have two glossaries being proposed [1] [2], and they don't
> have much in common with each other.  What to do now?  If we can get the
> authors to agree on what patch to submit, we can move forward.
>
> I suggest to make a glossary be 0001, and then the other patches can be
> 0002 or further.

Yes, we should work on the glossary with priority because other things 
depend on it, not only the explanation of figures.

The two proposals differs in their nature: [1] is focused on PG-specific 
terms like WAL, Background Writer, Background Worker, ... and such terms 
that are broadly used but may differ from the meaning in other DBMS like 
Segment or Data Dictionary. It's only a starting point. Currently it 
misses the terms of important features like MVCC, Backup, Replication, 
... .  [2] also contains fundamental terms but is focused on universal 
terms of the DBMS community like SELECT, Null, Rollback, ... .

It's important to check, whether the existing documentation starts with 
something like "A <glossary-term> is a ...". In my opinion such 
redundancies aren't a problem as long as they don't contradict each 
other. On the contrary, I support this approach.

J. Purtz

view thread (7+ messages)

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Shrinking SVG (Again)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox