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

From Amit Langote
Subject Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 releasenotes.
Date
Msg-id 3a4dcc63-2dfe-3e94-3325-39d491384c09@lab.ntt.co.jp
Whole thread Raw
In response to [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 release notes.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 release notes.  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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

[1] https://commitfest.postgresql.org/14/1023/

Attachment

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 release notes.
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Doc: desultory copy-editing for v10 release notes.