From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Doc: in back branches, don't call it a row constructor if it isn |
Date: | 2016-11-22 23:07:54 |
Message-ID: | E1c9KAM-0005aa-SN@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: in back branches, don't call it a row constructor if it isn't really.
Before commit 906bfcad7, we were not actually processing the righthand
side of a multiple-column assignment in UPDATE as a row constructor:
it was just a parenthesized list of expressions. Call it that rather
than risking confusion by people who would expect the documented behaviors
of row constructors to apply.
Back-patch to 9.5; before that, the text correctly described the construct
as a "list of independent expressions".
Discussion: <16288(dot)1479610770(at)sss(dot)pgh(dot)pa(dot)us>
Branch
------
REL9_5_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/3de257f602550407ba095189feb6d3db8cd02b22
Modified Files
--------------
doc/src/sgml/ref/update.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-11-22 23:35:28 | Re: [COMMITTERS] pgsql: Doc: improve documentation about composite-value usage. |
Previous Message | Tom Lane | 2016-11-22 22:56:58 | pgsql: Doc: improve documentation about composite-value usage. |