postgres.git / summary / log / commit / refs

commit    2a975b991e44ec6b3ac39612869176fdbd3c0db2
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Fri May 15 22:32:33 2026 +0000

    Doc: fix release-note typo.
    
    This mention of memcpy() should of course have said memcmp().
    
    Reported-by: chris@chrullrich.net
    Author: Tom Lane <tgl@sss.pgh.pa.us>
    Discussion: https://postgr.es/m/177883653690.764749.14038057906859461991@wrigleys.postgresql.org
    Backpatch-through: 14


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

diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml
index 3e8b4dc39c4..4975d446337 100644
--- a/doc/src/sgml/release-15.sgml
+++ b/doc/src/sgml/release-15.sgml
@@ -293,7 +293,7 @@ Branch: REL_14_STABLE [b282280e9] 2026-05-11 05:13:51 -0700
 
      <para>
       Use <function>timingsafe_bcmp()</function> instead
-      of <function>memcpy()</function> or <function>strcmp()</function>
+      of <function>memcmp()</function> or <function>strcmp()</function>
       when checking passwords, hashes, etc.  It is not known whether the
       data dependency of those functions is usefully exploitable in any of
       these places, but in the interests of safety, replace them.


[parent: 4503c9771683]