Re: New "single-call SRF" APIs are very confusingly named

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: New "single-call SRF" APIs are very confusingly named
Дата
Msg-id Y04IlflJ3xjouvVF@paquier.xyz
обсуждение исходный текст
Ответ на Re: New "single-call SRF" APIs are very confusingly named  (Michael Paquier <michael@paquier.xyz>)
Список 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

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] Allow usage of archive .backup files as backup_label
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Switching XLog source from archive to streaming when primary available