Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
doc: Fix incorrect reference to textout in plpgsql examples
authorMichael Paquier <michael@paquier.xyz>
Sun, 5 Jul 2020 10:36:12 +0000 (19:36 +0900)
committerMichael Paquier <michael@paquier.xyz>
Sun, 5 Jul 2020 10:36:12 +0000 (19:36 +0900)
This error has survived for 22 years, and has been introduced by
da63386.

Reported-by: Erwin Brandstetter
Discussion: https://postgr.es/m/CAGHENJ57wogGOvGXo5LgWYcqswxafLck8ELqHDR+zrkTPgs_OQ@mail.gmail.com
Backpatch-through: 9.5

doc/src/sgml/plpgsql.sgml

index 05d2705604b5a9f813c4b42747632c4534c53e70..d5c1654b16e4f3f244b69a02fa727a19bae3a9e9 100644 (file)
@@ -4892,7 +4892,7 @@ $$ LANGUAGE plpgsql;
      to the local variable <varname>curtime</varname>, the
      <application>PL/pgSQL</application> interpreter casts this
      string to the <type>timestamp</type> type by calling the
-     <function>text_out</function> and <function>timestamp_in</function>
+     <function>textout</function> and <function>timestamp_in</function>
      functions for the conversion.  So, the computed time stamp is updated
      on each execution as the programmer expects.  Even though this
      happens to work as expected, it's not terribly efficient, so