mirror of
https://github.com/timescale/timescaledb.git
synced 2025-05-15 18:13:18 +08:00
c715d96aa4
Logging and caching related tables from the timescaledb extension should not be dumped using pg_dump. Our scripts specify a few such unwanted tables. Apart from being unnecessary, the "job_errors" had some restricted permissions causing additional problems in pg_dump. We now don't include such tables for dumping. Fixes #5449
23 lines
1.0 KiB
SQL
23 lines
1.0 KiB
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.
|
|
|
|
-- This file contains infrastructure for cache invalidation of TimescaleDB
|
|
-- metadata caches kept in C. Please look at cache_invalidate.c for a
|
|
-- description of how this works.
|
|
CREATE TABLE _timescaledb_cache.cache_inval_hypertable();
|
|
|
|
-- For notifying the scheduler of changes to the bgw_job table.
|
|
CREATE TABLE _timescaledb_cache.cache_inval_bgw_job();
|
|
|
|
-- This is pretty subtle. We create this dummy cache_inval_extension table
|
|
-- solely for the purpose of getting a relcache invalidation event when it is
|
|
-- deleted on DROP extension. It has no related triggers. When the table is
|
|
-- invalidated, all backends will be notified and will know that they must
|
|
-- invalidate all cached information, including catalog table and index OIDs,
|
|
-- etc.
|
|
CREATE TABLE _timescaledb_cache.cache_inval_extension();
|
|
|
|
GRANT SELECT ON ALL TABLES IN SCHEMA _timescaledb_cache TO PUBLIC;
|
|
|