Re: function calls optimization

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,Andrzej Barszcz <abusinf(at)gmail(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: function calls optimization
Date: 2019-10-31 14:25:06
Message-ID: 067303FD-BA50-4036-A097-2E179D190FFD@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On October 31, 2019 7:06:13 AM PDT, Andrzej Barszcz <abusinf(at)gmail(dot)com> wrote:
>Hi
>
>I almost finished patch optimizing non volatile function calls.
>
>select f(t.n) from t where f(t.n) > 10 and f(t.n) < 100; needs 3 calls
>of
>f() for each tuple,
>after applying patch only 1.
>
>Any pros and cons ?

Depends on the actual way of implementing this proposal. Think we need more details than what you idea here.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-10-31 14:45:26 Re: function calls optimization
Previous Message Masahiko Sawada 2019-10-31 14:24:37 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)