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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Improve parser's and planner's handling of set-returning functio
Date: 2016-09-13 18:09:42
Message-ID: CAM3SWZQA29ECCNeuYj-TW-exuN=pN8hzb1Te6_gmmHrYi3PyNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-09-13 18:25:42 pgsql: Fix executor/README to reflect disallowing SRFs in UPDATE.
Previous Message Tom Lane 2016-09-13 17:54:39 pgsql: Improve parser's and planner's handling of set-returning functio