Re: New "single-call SRF" APIs are very confusingly named - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: New "single-call SRF" APIs are very confusingly named
Date
Msg-id Y04IlflJ3xjouvVF@paquier.xyz
Whole thread Raw
In response to Re: New "single-call SRF" APIs are very confusingly named  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Mon, Oct 17, 2022 at 10:13:33AM +0900, Michael Paquier wrote:
> That's just assign_record_type_typmod(), which would make sure to fill
> the cache for a RECORD tupdesc.  How about "fill the cache with the
> information of the tuple descriptor type, for a transient RECORD
> datatype"?  If you have a better, somewhat less confusing, idea, I am
> open to suggestions.

At the end, I was unhappy with this formulation, so I have just
mentioned what the top of BlessTupleDesc() tells, with the name of
the function used on the tuple descriptor when the flag is activated
by the init call.

The compatibility functions have been removed from HEAD, by the way.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] Allow usage of archive .backup files as backup_label
Next
From: Bharath Rupireddy
Date:
Subject: Re: Switching XLog source from archive to streaming when primary available