| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add A Glossary |
| Date: | 2020-04-02 01:41:11 |
| Message-ID: | 20200402014111.GA9466@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 2020-Apr-01, Justin Pryzby wrote:
> planner/optimizer: ...
I propose we define "planner" and make "optimizer" a <glosssee> entry.
I further propose not to define the term "normalized", at least not for
now. That seems a very deep rabbit hole.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2020-04-02 03:34:31 | Re: Add A Glossary |
| Previous Message | Justin Pryzby | 2020-04-02 01:09:34 | Re: Add A Glossary |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | movead.li@highgo.ca | 2020-04-02 01:41:48 | Re: recovery_target_action=pause with confusing hint |
| Previous Message | Justin Pryzby | 2020-04-02 01:33:44 | Re: control max length of parameter values logged |