On 2018-Jul-06, Amit Langote wrote:
> On 2018/07/06 6:55, David Rowley wrote:
> > On 6 July 2018 at 09:41, Alvaro Herrera wrote:
> >> On 2018-Jul-05, Peter Eisentraut wrote:
> >>> Committed.
> >>
> >> Thanks for handling this.
> >>
> >> Should we do this in REL_11_STABLE too? I vote yes.
> >
>
On 2018/07/06 6:55, David Rowley wrote:
> On 6 July 2018 at 09:41, Alvaro Herrera wrote:
>> On 2018-Jul-05, Peter Eisentraut wrote:
>>> Committed.
>>
>> Thanks for handling this.
>>
>> Should we do this in REL_11_STABLE too? I vote yes.
>
> Sorry for now paying much attention to this, but I've
On 6 July 2018 at 09:41, Alvaro Herrera wrote:
> On 2018-Jul-05, Peter Eisentraut wrote:
>> Committed.
>
> Thanks for handling this.
>
> Should we do this in REL_11_STABLE too? I vote yes.
Sorry for now paying much attention to this, but I've read through
what's been committed and I also think
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
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
>>>
On Fri, Jun 01, 2018 at 03:00:10PM -0400, Alvaro Herrera wrote:
> On 2018-May-23, Justin Pryzby wrote:
>
> > There's two other, wider changes to consider:
...
>
> > - should we find a unified term for "inheritence-based partitioning" and
> > avoid
> >using the word "partitioning" in that
