Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit9dd1101

Browse files
danielgustafssonpull[bot]
authored andcommitted
Reword memory terminology for PQresultMemorySize
Rather than using the generic word "space" we might as well use "memory"since that's precisely what we're dealing with here.This was extracted from a larger patch around terminology changes wherethe remaining hunks were rejected.Author: Gurjeet Singh <gurjeet@singh.im>Reviewed-by: Daniel Gustafsson <daniel@yesql.se>Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>Discussion:https://postgr.es/m/CABwTF4UHO_NtcsOL6_XZfnpKg_0XBFKa7B-7_x5zs3MRZm3-Tg@mail.gmail.com
1 parent1dce018 commit9dd1101

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎doc/src/sgml/libpq.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7323,7 +7323,7 @@ size_t PQresultMemorySize(const PGresult *res);
73237323
<para>
73247324
This value is the sum of all <function>malloc</function> requests
73257325
associated with the <structname>PGresult</structname> object, that is,
7326-
all thespace that will be freed by <xref linkend="libpq-PQclear"/>.
7326+
all thememory that will be freed by <xref linkend="libpq-PQclear"/>.
73277327
This information can be useful for managing memory consumption.
73287328
</para>
73297329
</listitem>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp