mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-16 06:31:10 +02:00
029fac2264
It was never terribly consistent to use OR REPLACE (because of the lack of comparable functionality for data types, operators, etc), and experimentation shows that it's now positively pernicious in the extension world. We really want a failure to occur if there are any conflicts, else it's unclear what the extension-ownership state of the conflicted object ought to be. Most of the time, CREATE EXTENSION will fail anyway because of conflicts on other object types, but an extension defining only functions can succeed, with bad results.
23 lines
572 B
SQL
23 lines
572 B
SQL
/* contrib/dict_int/dict_int--1.0.sql */
|
|
|
|
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';
|