From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Doc: desultory copy-editing for v10 release notes. |
Date: | 2017-07-10 01:09:40 |
Message-ID: | 3a4dcc63-2dfe-3e94-3325-39d491384c09@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 2017/07/10 9:11, Tom Lane wrote:
> Doc: desultory copy-editing for v10 release notes.
>
> Improve many item descriptions, improve markup, relocate some items
> that seemed to be in the wrong section.
>
> Branch
> ------
> master
>
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/749eceff4a1f9740391b126c81af9fd4bf3b1eaa
I see you updated text for the partitioning item:
@@ -1574,7 +1553,7 @@
<para>
Add table <link linkend="SQL-CREATETABLE-PARTITION">partitioning
syntax</> that automatically creates partition constraints and
- <command>INSERT</> routing (Amit Langote)
+ handles routing of tuple insertions and updates (Amit Langote)
</para>
Although I like the new text better, I'm afraid that we don't support
routing updates yet, only inserts.
create table p (a int) partition by list (a);
create table p1 partition of p for values in (1);
insert into p values (1);
update p set a = a + 1;
ERROR: new row for relation "p1" violates partition constraint
DETAIL: Failing row contains (2).
Routing of updates is being worked on for PG 11 [1].
Attached patch removes "and updates".
Thanks,
Amit
Attachment | Content-Type | Size |
---|---|---|
no-update-routing-in-10.patch | text/plain | 520 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-07-10 03:36:44 | Re: pgsql: Doc: desultory copy-editing for v10 release notes. |
Previous Message | Tom Lane | 2017-07-10 00:11:43 | pgsql: Doc: desultory copy-editing for v10 release notes. |