Re: Proposal: add new API to stringinfo
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgsql-hackers@postgresql.org
Date: 2024-12-26T03:37:12Z
Lists: pgsql-hackers
On Thu, Dec 26, 2024 at 09:53:09AM +0900, Tatsuo Ishii wrote: >> Saying that, having more control over the initial >> size used for a StringInfo could provide better practices in some >> cases. This reminds me of the ALLOCSET_SMALL_* fields in memutils.h, >> hence an idea would be an initStringInfoExtended() that you could >> combine with two #define two: one for the "default" of 1024 and a >> second one for "small", like 32 or 64 (?), that can be used at will >> with the new API call. Then you could switch initStringInfo() to >> become a macro of the new "extended" call. Just an idea. > > But then the extensions that use stringinfo.c need to be recompiled? New APIs are materials for HEAD, so recompilation needs to happen anyway. Using a macro makes things slightly simpler and it would not break unnecessarily the compilation of existing extensions. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add new StringInfo APIs to allow callers to specify the buffer size.
- a9dcbb4d5c00 18.0 landed