|From:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|To:||Corey Huinker <corey(dot)huinker(at)gmail(dot)com>|
|Cc:||Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: Add A Glossary|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2020-Apr-01, Corey Huinker wrote:
> > I propose we define "planner" and make "optimizer" a <glosssee> entry.
> I have no objection to more entries, or edits to entries, but am concerned
> that the process leads to someone having to manually merge several
> start-from-scratch patches, with no clear sense of when we'll be done. I
> may make sense to appoint an edit-collector.
I added "query planner" (please suggest edits) and "query" (using
Justin's def) and edited the defs of the ACID terms a little bit (in
particular moved the definition of atomic transaction to "atomicity"
from "atomic", and made the latter reference the former instead of the
other way around). Also removed "Aggregating" as suggested upthread. I
moved "master" over to "primary (server)", keeping the ref; we don't use
the former much.
There's only one "serious" mistake in the defs AFAICS which is that of
"global objects". Only roles, tablespace, databases are global objects.
Objects that are not in a schema (extensions, etc) are not "global" in
I think all <glossterm> used in definitions should have linkend.
I hope to get this committed today, but I'm going to sleep now so if you
want to suggest further edits, now's the time. I think the terms
proposed by Justin are good to have -- please discuss the defs he
proposed -- only "normalized" I'd rather stay away from.
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
|Next Message||Jürgen Purtz||2020-04-02 12:44:26||Re: Add A Glossary|
|Previous Message||Corey Huinker||2020-04-02 03:44:56||Re: Add A Glossary|
|Next Message||Prabhat Sahu||2020-04-02 08:45:44||Re: [Proposal] Global temporary tables|
|Previous Message||Julien Rouhaud||2020-04-02 08:30:35||Re: WAL usage calculation patch|