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:34 +0000 (19:36 +0900)
committerMichael Paquier <michael@paquier.xyz>
Sun, 5 Jul 2020 10:36:34 +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 3fdb8cbda2a92aefd54d9364c4deb2d223c3a6df..35623a3f6548d9d757e36702e19a7c304bc4a5ad 100644 (file)
@@ -4654,7 +4654,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