From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Doc: desultory copy-editing for v10 release notes. |
Date: | 2017-07-10 03:36:44 |
Message-ID: | 1072.1499657804@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-07-10 04:09:14 | pgsql: Doc: clarify wording about tool requirements in sourcerepo.sgml. |
Previous Message | Amit Langote | 2017-07-10 01:09:40 | Re: pgsql: Doc: desultory copy-editing for v10 release notes. |