mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-15 21:51:10 +02:00
5484c0a980
Extension scripts should never use CREATE OR REPLACE for initial object creation. If there is a collision with a pre-existing (probably user-created) object, we want extension installation to fail, not silently overwrite the user's object. Bloom and sslinfo both violated this precept. Also fix a number of scripts that had no standard header (the file name comment and the \echo...\quit guard). Probably the \echo...\quit hack is less important now than it was in 9.1 days, but that doesn't mean that individual extensions get to choose whether to use it or not. And fix a couple of evident copy-and-pasteos in file name comments. No need for back-patch: the REPLACE bugs are both new in 9.6, and the rest of this is pretty much cosmetic. Andreas Karlsson and Tom Lane
18 lines
540 B
SQL
18 lines
540 B
SQL
/* contrib/ltree_plpython/ltree_plpython2u--1.0.sql */
|
|
|
|
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
|
|
\echo Use "CREATE EXTENSION ltree_plpython2u" to load this file. \quit
|
|
|
|
-- make sure the prerequisite libraries are loaded
|
|
LOAD 'plpython2';
|
|
SELECT NULL::ltree;
|
|
|
|
|
|
CREATE FUNCTION ltree_to_plpython2(val internal) RETURNS internal
|
|
LANGUAGE C STRICT IMMUTABLE
|
|
AS 'MODULE_PATHNAME', 'ltree_to_plpython';
|
|
|
|
CREATE TRANSFORM FOR ltree LANGUAGE plpython2u (
|
|
FROM SQL WITH FUNCTION ltree_to_plpython2(internal)
|
|
);
|