Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit d8fd08e

Browse files
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 where the 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 parent 66d6086 commit d8fd08e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/src/sgml/libpq.sgml

+1-1
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 the space that will be freed by <xref linkend="libpq-PQclear"/>.
7326+
all the memory 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)