postgres.git / summary / log / commit / refs

commit    d8fd08efbc660788f9e735f9dda824c64bc9bd6b
Author:   Daniel Gustafsson <dgustafsson@postgresql.org>
Date:     Tue Oct 24 20:18:19 2023 +0000
First released in: 17.0

    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


 doc/src/sgml/libpq.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index a52baa27d56..64b2910feef 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -7323,7 +7323,7 @@ size_t PQresultMemorySize(const PGresult *res);
      <para>
       This value is the sum of all <function>malloc</function> requests
       associated with the <structname>PGresult</structname> object, that is,
-      all the space that will be freed by <xref linkend="libpq-PQclear"/>.
+      all the memory that will be freed by <xref linkend="libpq-PQclear"/>.
       This information can be useful for managing memory consumption.
      </para>
     </listitem>


[parent: 66d6086cbcbf]