From 36a1ba9d5e25d74fb50dfaccefe86f406f337a74 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 4 Jun 2011 23:12:27 +0300
Subject: [PATCH] Fix documentation reference to "above" example

found by Thom Brown
---
 doc/src/sgml/plpython.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index ffc1d3ab3d..eda2bbf34c 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -400,7 +400,8 @@ $$ LANGUAGE plpythonu;
    If an SQL null value<indexterm><primary>null value</primary><secondary
    sortas="PL/Python">in PL/Python</secondary></indexterm> is passed to a
    function, the argument value will appear as <symbol>None</symbol> in
-   Python. The above function definition will return the wrong answer for null
+   Python. For example, the function definition of <function>pymax</function>
+   shown in <xref linkend="plpython-funcs"> will return the wrong answer for null
    inputs. We could add <literal>STRICT</literal> to the function definition
    to make <productname>PostgreSQL</productname> do something more reasonable:
    if a null value is passed, the function will not be called at all,
-- 
2.11.0