mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-15 22:21:08 +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.
17 lines
345 B
SQL
17 lines
345 B
SQL
/* contrib/spi/timetravel--1.0.sql */
|
|
|
|
CREATE FUNCTION timetravel()
|
|
RETURNS trigger
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C;
|
|
|
|
CREATE FUNCTION set_timetravel(name, int4)
|
|
RETURNS int4
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C RETURNS NULL ON NULL INPUT;
|
|
|
|
CREATE FUNCTION get_timetravel(name)
|
|
RETURNS int4
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C RETURNS NULL ON NULL INPUT;
|