From: Robert Haas <rhaas@postgresql.org>
Date: Sat, 25 Dec 2010 03:21:50 +0000 (-0500)
Subject: Correct spelling: longjump() -> longjmp().
X-Git-Tag: REL9_0_3~24
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a45e2e141d5002866f60b6f28f14d00317c106d1;p=postgresql

Correct spelling: longjump() -> longjmp().
---

diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml
index 737a0d7f4d..19028a6cce 100644
--- a/doc/src/sgml/extend.sgml
+++ b/doc/src/sgml/extend.sgml
@@ -322,7 +322,7 @@
        If calling backend functions from C++ code, be sure that the
        C++ call stack contains only plain old data structures
        (<acronym>POD</>).  This is necessary because backend errors
-       generate a distant <function>longjump()</> that does not properly
+       generate a distant <function>longjmp()</> that does not properly
        unroll a C++ call stack with non-POD objects.
       </para>
      </listitem>