diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-10-30 16:44:26 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-10-30 16:44:26 -0400 |
| commit | 86182b18957b8f9e8045d55b137aeef7c9af9916 (patch) | |
| tree | 8cc03285e61d5c9ddc616e1eeeb85362ca75635f /src/backend/access/gist/gistvacuum.c | |
| parent | be72b9c378bfe99a3d175c98d36dc150229f4faf (diff) | |
| download | postgresql-86182b18957b8f9e8045d55b137aeef7c9af9916.tar.gz postgresql-86182b18957b8f9e8045d55b137aeef7c9af9916.zip | |
Doc: call out UPDATE syntax change as a v10 compatibility issue.
The change made by commit 906bfcad7 means that if you're writing
a parenthesized column list in UPDATE ... SET, but that column list
is only one column, you now need to write ROW(expression) on the
righthand side, not just a parenthesized expression. This was an
intentional change for spec compatibility and potential future
expansion of the possibilities for the RHS, but I'd neglected to
document it as a compatibility issue, figuring that hardly anyone
would bother with parenthesized syntax for a single target column.
I was wrong, as shown by questions from Justin Pryzby, Adam Brusselback,
and others. Move the release note item into the compatibility section
and point out the behavior change for a single target column.
Discussion: https://postgr.es/m/CAMjNa7cDLzPcs0xnRpkvqmJ6Vb6G3EH8CYGp9ZBjXdpFfTz6dg@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions