From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add A Glossary |
Date: | 2020-04-02 03:44:56 |
Message-ID: | CADkLM=f7jadk1bXrZc5F0gYsry+K9bCCeW=oUsVXa7J=3kd4dQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
>
> 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 further propose not to define the term "normalized", at least not for
> now. That seems a very deep rabbit hole.
>
+1 I think we appointed a guy named Xeno to work on that definition. He
says he's getting close...
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-04-02 08:43:28 | Re: Add A Glossary |
Previous Message | Corey Huinker | 2020-04-02 03:34:31 | Re: Add A Glossary |
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2020-04-02 03:51:29 | Re: [HACKERS] WAL logging problem in 9.4.3? |
Previous Message | Dilip Kumar | 2020-04-02 03:43:05 | Re: pg_stat_statements issue with parallel maintenance (Was Re: WAL usage calculation patch) |