Re: Use get_call_result_type() more widely
| От | Tom Lane |
|---|---|
| Тема | Re: Use get_call_result_type() more widely |
| Дата | |
| Msg-id | 1125757.1671523899@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Use get_call_result_type() more widely (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Use get_call_result_type() more widely
|
| Список | pgsql-hackers |
Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Dec 19, 2022 at 07:41:27PM +0530, Bharath Rupireddy wrote:
>> 0002 - gets rid of an unnecessary call to BlessTupleDesc()
>> after get_call_result_type().
> Hmm. I am not sure whether this is right, actually..
Hmm ... at least one of the paths through internal_get_result_type
is intentionally blessing the result tupdesc:
if (tupdesc->tdtypeid == RECORDOID &&
tupdesc->tdtypmod < 0)
assign_record_type_typmod(tupdesc);
but it's not clear if they all do, and the comments certainly
aren't promising it.
I'd be in favor of making this a documented API promise,
but it isn't that right now.
regards, tom lane
В списке pgsql-hackers по дате отправления: