Re: pgsql: Improve parser's and planner's handling of set-returning functio - Mailing list pgsql-committers

From Peter Geoghegan
Subject Re: pgsql: Improve parser's and planner's handling of set-returning functio
Date
Msg-id CAM3SWZQA29ECCNeuYj-TW-exuN=pN8hzb1Te6_gmmHrYi3PyNA@mail.gmail.com
Whole thread Raw
In response to pgsql: Improve parser's and planner's handling of set-returning functio  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Improve parser's and planner's handling of set-returning functio  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Tue, Sep 13, 2016 at 10:54 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> There is one case the parser will now throw error for although previous
> versions allowed it, which is SRFs in the tlist of an UPDATE.  That never
> behaved sensibly (since it's ill-defined which generated row should be
> used to perform the update) and it's hard to see why it should not be
> treated as an error.  It's a release-note-worthy change though.

There is a reference to this right at the end of the executor README
that was missed.


--
Peter Geoghegan


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Improve parser's and planner's handling of set-returning functio
Next
From: Tom Lane
Date:
Subject: pgsql: Fix executor/README to reflect disallowing SRFs in UPDATE.