From 56328de6e8457b075136c67795b24cd8568cbd05 Mon Sep 17 00:00:00 2001
From: Noah Misch <noah@leadboat.com>
Date: Fri, 23 Mar 2018 20:31:03 -0700
Subject: [PATCH] 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).
---
doc/src/sgml/extend.sgml | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml
index 354ad7a8021..8ee3fa0766b 100644
--- a/doc/src/sgml/extend.sgml
+++ b/doc/src/sgml/extend.sgml
@@ -884,13 +884,12 @@ SELECT * FROM pg_extension_update_paths('<replaceable>extension_name</>');
-- 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)