Re: Use get_call_result_type() more widely - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Use get_call_result_type() more widely
Date
Msg-id CA+TgmoY8XM5gp=QgsJKNp7tR_P9H4ZapLKNPPgsU6y3ehOrE3g@mail.gmail.com
Whole thread Raw
In response to Re: Use get_call_result_type() more widely  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Use get_call_result_type() more widely  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Mon, Dec 19, 2022 at 4:21 PM Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Error-safe user functions
Next
From: Corey Huinker
Date:
Subject: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions