From ab931303561da5244ba21f0f8fbe4a9ec837160d 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-17.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml
index 9bad665531e..207d42713c6 100644
--- a/doc/src/sgml/release-17.sgml
+++ b/doc/src/sgml/release-17.sgml
@@ -347,7 +347,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.