mirror of
https://github.com/timescale/timescaledb.git
synced 2025-05-15 10:11:29 +08:00
a4081516ca
Postgres will prepend pg_temp to the effective search_path if it is not present in the search_path. While pg_temp will never be used to look up functions or operators unless explicitly requested pg_temp will be used to look up relations. Putting pg_temp in search_path makes sure objects in pg_temp will be considered last and pg_temp cannot be used to mask existing objects.
16 lines
622 B
SQL
16 lines
622 B
SQL
-- This file and its contents are licensed under the Apache License 2.0.
|
|
-- Please see the included NOTICE for copyright information and
|
|
-- LICENSE-APACHE for a copy of the license.
|
|
|
|
SET LOCAL search_path TO pg_catalog, pg_temp;
|
|
|
|
CREATE SCHEMA _timescaledb_catalog;
|
|
CREATE SCHEMA _timescaledb_internal;
|
|
CREATE SCHEMA _timescaledb_cache;
|
|
CREATE SCHEMA _timescaledb_config;
|
|
CREATE SCHEMA timescaledb_experimental;
|
|
CREATE SCHEMA timescaledb_information;
|
|
|
|
GRANT USAGE ON SCHEMA _timescaledb_cache, _timescaledb_catalog, _timescaledb_internal, _timescaledb_config, timescaledb_information, timescaledb_experimental TO PUBLIC;
|
|
|