Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 release notes. - Mailing list pgsql-committers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 release notes.
Date
Msg-id 1072.1499657804@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 releasenotes.  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 releasenotes.  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-committers
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> On 2017/07/10 9:11, Tom Lane wrote:
>> Doc: desultory copy-editing for v10 release notes.

> I see you updated text for the partitioning item:

>         syntax</> that automatically creates partition constraints and
> -       <command>INSERT</> routing (Amit Langote)
> +       handles routing of tuple insertions and updates (Amit Langote)

> Although I like the new text better, I'm afraid that we don't support
> routing updates yet, only inserts.

Hm?  We correctly handle updates that don't change the partition key
columns, as well as deletes, no?  The previous text made it sound
like *only* the insert case worked properly.

It might be worth mentioning that you can't move a row into another
partition via UPDATE.  Or maybe that's more detail than we need here.
Not sure.

            regards, tom lane


pgsql-committers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 releasenotes.
Next
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Doc: clarify wording about tool requirements insourcerepo.sgml.