On Tue, Sep 13, 2016 at 10:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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