mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-13 10:31:50 +02:00
458857cc9d
We have seen one too many reports of people trying to use 9.1 extension files in the old-fashioned way of sourcing them in psql. Not only does that usually not work (due to failure to substitute for MODULE_PATHNAME and/or @extschema@), but if it did work they'd get a collection of loose objects not an extension. To prevent this, insert an \echo ... \quit line that prints a suitable error message into each extension script file, and teach commands/extension.c to ignore lines starting with \echo. That should not only prevent any adverse consequences of loading a script file the wrong way, but make it crystal clear to users that they need to do it differently now. Tom Lane, following an idea of Andrew Dunstan's. Back-patch into 9.1 ... there is not going to be much value in this if we wait till 9.2.
26 lines
711 B
SQL
26 lines
711 B
SQL
/* contrib/dict_int/dict_int--1.0.sql */
|
|
|
|
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
|
|
\echo Use "CREATE EXTENSION dict_int" to load this file. \quit
|
|
|
|
CREATE FUNCTION dintdict_init(internal)
|
|
RETURNS internal
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C STRICT;
|
|
|
|
CREATE FUNCTION dintdict_lexize(internal, internal, internal, internal)
|
|
RETURNS internal
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C STRICT;
|
|
|
|
CREATE TEXT SEARCH TEMPLATE intdict_template (
|
|
LEXIZE = dintdict_lexize,
|
|
INIT = dintdict_init
|
|
);
|
|
|
|
CREATE TEXT SEARCH DICTIONARY intdict (
|
|
TEMPLATE = intdict_template
|
|
);
|
|
|
|
COMMENT ON TEXT SEARCH DICTIONARY intdict IS 'dictionary for integers';
|