postgres/timescaledb
1
0
Fork 0
mirror of https://github.com/timescale/timescaledb.git synced 2025-05-15 01:53:41 +08:00
Code Issues Packages Projects Releases Wiki Activity

Clean up dead code

Browse Source
This commit is contained in:
Markos Fountoulakis 2022-01-03 14:30:39 +02:00 committed by Markos Fountoulakis
parent 0dd4329ab1
commit 4762908bc8
2 changed files with 0 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
cmake/ScriptFiles.cmake
View File

@ -20,12 +20,6 @@ set(PRE_INSTALL_SOURCE_FILES
pre_install/fdw_functions.sql
pre_install/timescaledb_fdw.sql)
# Things like aggregate functions cannot be REPLACEd and really need to be
# created just once(like PRE_INSTALL_SOURCE_FILES) but unlike
# PRE_INSTALL_SOURCE_FILES these have to be loaded after everything else is
# loaded.
set(IMMUTABLE_API_SOURCE_FILES aggregates.sql)
# The rest of the source files defining mostly functions
set(SOURCE_FILES
pre_install/types.functions.sql

5
sql/updates/README.md
View File

@ -39,11 +39,6 @@ to consider.
4. The creation of new metadata tables need to be part of modfiles,
similar to `ALTER`s of such tables. Otherwise, later modfiles
cannot rely on those tables being present.
5. When creating a new aggregate, the `CREATE` statement should be
added to both aggregate.sql AND an update file. aggregate.sql is
run once when TimescaleDB is installed so adding a definition in
an update file is the only way to ensure that upgrading users get
the new function.
Notes on post_update.sql
We use a special config var (timescaledb.update_script_stage )