mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-15 19:51:09 +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
554 B
SQL
23 lines
554 B
SQL
/* contrib/dict_xsyn/dict_xsyn--1.0.sql */
|
|
|
|
CREATE FUNCTION dxsyn_init(internal)
|
|
RETURNS internal
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C STRICT;
|
|
|
|
CREATE FUNCTION dxsyn_lexize(internal, internal, internal, internal)
|
|
RETURNS internal
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C STRICT;
|
|
|
|
CREATE TEXT SEARCH TEMPLATE xsyn_template (
|
|
LEXIZE = dxsyn_lexize,
|
|
INIT = dxsyn_init
|
|
);
|
|
|
|
CREATE TEXT SEARCH DICTIONARY xsyn (
|
|
TEMPLATE = xsyn_template
|
|
);
|
|
|
|
COMMENT ON TEXT SEARCH DICTIONARY xsyn IS 'eXtended synonym dictionary';
|