Re: Replace references to malloc() in libpq documentation with generic language
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Gurjeet Singh <gurjeet@singh.im>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2023-10-24T08:32:58Z
Lists: pgsql-hackers
> On 24 Oct 2023, at 07:13, Gurjeet Singh <gurjeet@singh.im> wrote: > The user does not benefit from knowing that libpq allocates some/all memory > using malloc(). Mentioning malloc() here has a few downsides, and almost no > benefits. I'm not entirely convinced that replacing "malloc" with "allocated on the heap" improves the documentation. I do agree with this proposed change though: - all the space that will be freed by <xref linkend="libpq-PQclear"/>. + all the memory that will be freed by <xref linkend="libpq-PQclear"/>. -- Daniel Gustafsson
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Reword memory terminology for PQresultMemorySize
- d8fd08efbc66 17.0 landed