From d472bf14f2595926a96bf668936b2cc920b9a7d3 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 15 May 2026 18:32:33 -0400
Subject: [PATCH] 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-18.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml
index 9537f1932ec..222d884831b 100644
--- a/doc/src/sgml/release-18.sgml
+++ b/doc/src/sgml/release-18.sgml
@@ -369,7 +369,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.