Re: Letting plpgsql in on the fun with the new expression eval stuff

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Letting plpgsql in on the fun with the new expression eval stuff
Date: 2017-12-21 18:00:12
Message-ID: 30461.1513879212@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Dec 20, 2017 at 6:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Anyway, I left it as-is, but I'm willing to make the change if
>> people feel the other way is better.

> I feel the other way -- let's not add more pointer indirections if it
> isn't really necessary.

OK --- with any luck, the changes in the paramFetch API will force people
to update relevant code anyway. It would only be an issue for code that
is not calling paramFetch at all, and such code is broken anyway for
dynamic param lists.

Pushed without touching that issue.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tels 2017-12-21 18:17:45 Re: Bitmap table scan cost per page formula
Previous Message Andres Freund 2017-12-21 17:55:24 Re: ddd