Re: Use get_call_result_type() more widely

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use get_call_result_type() more widely
Date: 2022-12-19 22:50:03
Message-ID: CA+TgmoY8XM5gp=QgsJKNp7tR_P9H4ZapLKNPPgsU6y3ehOrE3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 19, 2022 at 4:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Now that somebody's made an effort to identify which places are
> potentially performance-critical, I don't see why we wouldn't use
> the fruits of their labor. Yes, somebody else might draw the line
> differently, but drawing a line at all seems like a step forward
> to me.

All right, well, I just work here. :-)

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2022-12-19 22:56:37 CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions
Previous Message Robert Haas 2022-12-19 22:48:53 Re: Error-safe user functions