Re: check_srf_call_placement() isn't always setting p_hasTargetSRFs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: check_srf_call_placement() isn't always setting p_hasTargetSRFs
Date: 2017-01-16 19:10:24
Message-ID: 21818.1484593824@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Is there a reason not to just set p_hasTargetSRFs once towards the end
> of the function, instead of doing so for all the non-error cases?

Yes: it's not supposed to get set when the SRF is in FROM.

> I wonder if there should be a seperate expression type for
> the INSERT ... VALUES(exactly-one-row); since that behaves quite
> differently.

Perhaps. Or maybe we should just use EXPR_KIND_SELECT_TARGET for that?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-01-16 19:13:18 Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)
Previous Message Alvaro Herrera 2017-01-16 19:04:34 Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)