Re: documentation fixes for partition pruning, round three - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: documentation fixes for partition pruning, round three
Date
Msg-id 20180705214128.hyacmxgf47kjkexq@alvherre.pgsql
Whole thread Raw
In response to Re: documentation fixes for partition pruning, round three  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: documentation fixes for partition pruning, round three  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
On 2018-Jul-05, Peter Eisentraut wrote:

> On 01.06.18 23:33, Justin Pryzby wrote:
> >>>  - 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.
> > 
> > I made changes to avoid "partition" (which I think should mean a child of
> > relkind='p', and itself of relkind='r') and "partitioned" (meaning relkind='p'
> > itself) but left alone most instances of "partitioning".
> 
> Committed.

Thanks for handling this.

Should we do this in REL_11_STABLE too?  I vote yes.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: patch to allow disable of WAL recycling
Next
From: Thomas Munro
Date:
Subject: Re: patch to allow disable of WAL recycling