diff options
| author | Noah Misch <noah@leadboat.com> | 2018-03-23 20:31:03 -0700 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2018-03-23 20:31:03 -0700 |
| commit | c92f7c62232c67b1a35ca5524a41a5cddfe66746 (patch) | |
| tree | be7a020f8471928cb15ac0834af5c6d6b2232eba | |
| parent | 52f3a9d6a32c0c070a15486c3aecbc4405d2da88 (diff) | |
Don't qualify type pg_catalog.text in extend-extensions-example.
Extension scripts begin execution with pg_catalog at the front of the
search path, so type names reliably refer to pg_catalog. Remove these
superfluous qualifications. Earlier <programlisting> of this <sect1>
already omitted them. Back-patch to 9.3 (all supported versions).
| -rw-r--r-- | doc/src/sgml/extend.sgml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6c043cdd02a..348ae71423f 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -1010,13 +1010,12 @@ SELECT * FROM pg_extension_update_paths('<replaceable>extension_name</replaceabl -- complain if script is sourced in psql, rather than via CREATE EXTENSION \echo Use "CREATE EXTENSION pair" to load this file. \quit -CREATE TYPE pair AS ( k pg_catalog.text, v pg_catalog.text ); +CREATE TYPE pair AS ( k text, v text ); -CREATE OR REPLACE FUNCTION pair(pg_catalog.text, pg_catalog.text) +CREATE OR REPLACE FUNCTION pair(text, text) RETURNS pair LANGUAGE SQL AS 'SELECT ROW($1, $2)::@extschema@.pair;'; -CREATE OPERATOR ~> (LEFTARG = pg_catalog.text, - RIGHTARG = pg_catalog.text, PROCEDURE = pair); +CREATE OPERATOR ~> (LEFTARG = text, RIGHTARG = text, PROCEDURE = pair); -- "SET search_path" is easy to get right, but qualified names perform better. CREATE OR REPLACE FUNCTION lower(pair) |