Re: documentation fixes for partition pruning, round two
От | Alvaro Herrera |
---|---|
Тема | Re: documentation fixes for partition pruning, round two |
Дата | |
Msg-id | 20180601190010.iqux2pa2jpw2cxl2@alvherre.pgsql обсуждение исходный текст |
Ответ на | documentation fixes for partition pruning, round two (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: documentation fixes for partition pruning, round three
|
Список | pgsql-hackers |
On 2018-May-23, Justin Pryzby wrote: > There's two other, wider changes to consider: > > - should "5.10.4. Partition Pruning" be moved after "5.10.2. Declarative > Partitioning", rather than after "5.10.3. Implementation Using Inheritance" ? I considered that when reorganizing this section, but it seemed more sensible to me to keep both pruning techniques together rather than put each one immediately below its partitioning technique. Maybe I'm wrong in that. > - should we find a unified term for "inheritence-based partitioning" and avoid > using the word "partitioning" in that context? For example: "Partitioning > can be implemented using table inheritance[...]". One possible phrase > currently begin used is: "legacy inheritance method". Yeah, maybe it'd be a good time to do that. In particular I wondered whether the section title "Partitioning and Constraint Exclusion" should be changed somehow to note the fact that it's mostly for the legacy method. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: