Re: function calls optimization

Hi,

On October 31, 2019 8:51:11 AM PDT, Andrzej Barszcz <abusinf(at)gmail(dot)com> wrote:
>x <> 0 is evaluated first, 1/x only when x <> 0, not ?
>
>czw., 31 paź 2019 o 16:45 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napisał(a):
>
>> Andres Freund <andres(at)anarazel(dot)de> writes:
>> > Potentially related note: for nodes like seqscan, combining the
>qual and
>> projection processing into one expression seems to be a noticable win
>(at
>> least when taking care do emit two different sets of deform
>expression
>> steps).
>>
>> There's just one problem: that violates SQL semantics, and not in
>> a small way.
>>
>> select 1/x from tab where x <> 0

On postgres lists the policy is to reply below the quoted bit, and to trim the quote appropriately.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.