Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: Use get_call_result_type() more widely
Date
Msg-id Y6Fmk2Y5d07MbdQx@paquier.xyz
Whole thread Raw
In response to Re: Use get_call_result_type() more widely  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Use get_call_result_type() more widely  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Mon, Dec 19, 2022 at 07:41:27PM +0530, Bharath Rupireddy wrote:
> I agree with the bucketization. Please see the attached patches. 0001
> - gets rid of explicit tuple desc creation using
> get_call_result_type() for functions thought to be not-so-frequently
> called.

It looks like I am OK with the code paths updated here, which refer to
none of the "critical" function paths.

> 0002 - gets rid of an unnecessary call to BlessTupleDesc()
> after get_call_result_type().

Hmm.  I am not sure whether this is right, actually..
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Use get_call_result_type() more widely
Next
From: Magnus Hagander
Date:
Subject: Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures