timescaledb | source time-series SQL database | Time Series Database library

 by   timescale C Version: 2.11.0 License: Non-SPDX

kandi X-RAY | timescaledb Summary

kandi X-RAY | timescaledb Summary

timescaledb is a C library typically used in Database, Time Series Database applications. timescaledb has no bugs, it has no vulnerabilities and it has medium support. However timescaledb has a Non-SPDX License. You can download it from GitHub.

TimescaleDB is an open-source database designed to make SQL scalable for time-series data. It is engineered up from PostgreSQL and packaged as a PostgreSQL extension, providing automatic partitioning across time and space (partitioning key), as well as full SQL support. If you prefer not to install or administer your instance of TimescaleDB, hosted versions of TimescaleDB are available in the cloud of your choice (pay-as-you-go, with a free trial to start). To determine which option is best for you, see Timescale Products for more information about our Apache-2 version, TimescaleDB Community (self-hosted), and Timescale Cloud (hosted), including: feature comparisons, FAQ, documentation, and support.

            kandi-support Support

              timescaledb has a medium active ecosystem.
              It has 15078 star(s) with 797 fork(s). There are 307 watchers for this library.
              It had no major release in the last 12 months.
              There are 490 open issues and 1927 have been closed. On average issues are closed in 146 days. There are 59 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of timescaledb is 2.11.0

            kandi-Quality Quality

              timescaledb has 0 bugs and 0 code smells.

            kandi-Security Security

              timescaledb has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              timescaledb code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              timescaledb has a Non-SPDX License.
              Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

            kandi-Reuse Reuse

              timescaledb releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.
              It has 424 lines of code, 34 functions and 6 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of timescaledb
            Get all kandi verified functions for this library.

            timescaledb Key Features

            No Key Features are available at this moment for timescaledb.

            timescaledb Examples and Code Snippets

            No Code Snippets are available at this moment for timescaledb.

            Community Discussions


            Finding out the size of a continuous aggregate
            Asked 2022-Mar-15 at 06:54

            Have hypertable table with a couple million rows. I'm able to select the size of this just fine using the following:

            SELECT pg_size_pretty( pg_total_relation_size('towns') );

            I also have a continuous aggregate for that hypertable:



            Answered 2021-Aug-04 at 14:29

            The following SQL can help :)

            Source https://stackoverflow.com/questions/68652129


            How to get pg_stat_user_tables n_tup_ins for timescale's compressed table?
            Asked 2022-Mar-11 at 13:32

            We have a Prometheus Postgres Exporter set up and expect we can get stats of rows inserted into table



            Answered 2022-Mar-11 at 13:32

            I'm not sure I understood what do you mean by "all affected tables", but to get all hypertables in a single query, you can cast the hypertable name with ::regclass. Example from some playground database with a few random hypertables:

            Source https://stackoverflow.com/questions/71410334


            TimescaleDB - get retention policy and chunk_time_interval for a table
            Asked 2022-Mar-07 at 12:15

            Given a hypertable



            Answered 2022-Mar-07 at 12:15

            You can get this information about retention policies through the jobs view:

            Source https://stackoverflow.com/questions/71354458


            start from hours and minutes with time_bucket_gapfill
            Asked 2022-Feb-17 at 05:31

            I have the next forecast table:



            Answered 2022-Feb-17 at 05:31

            I would use generate_series function.

            generate_series(start, stop, step interval)

            The third parameter you can write your expect interval. In your case that might be 1 hours

            Source https://stackoverflow.com/questions/71151754


            Have an ordinary table on a PostgreSQL TimescaleDB (timeseries) database
            Asked 2022-Jan-03 at 15:10

            For a project I need two types of tables.

            1. hypertable (which is a special type of table in PostgreSQL (in PostgreSQL TimescaleDB)) for some timeseries records
            2. my ordinary tables which are not timeseries

            Can I create a PostgreSQL TimescaleDB and store my ordinary tables on it? Are all the tables a hypertable (time series) on a PostgreSQL TimescaleDB? If no, does it have some overhead if I store my ordinary tables in PostgreSQL TimescaleDB?

            If I can, does it have any benefit if I store my ordinary table on a separate ordinary PostgreSQL database?



            Answered 2022-Jan-03 at 15:10

            Can I create a PostgreSQL TimescaleDB and store my ordinary tables on it?

            Absolutely... TimescaleDB is delivered as an extension to PostgreSQL and one of the biggest benefits is that you can use regular PostgreSQL tables alongside the specialist time-series tables. That includes using regular tables in SQL queries with hypertables. Standard SQL works, plus there are some additional functions that Timescale created using PostgreSQL's extensibility features.

            Are all the tables a hypertable (time series) on a PostgreSQL TimescaleDB?

            No, you have to explicitly create a table as a hypertable for it to implement TimescaleDB features. It would be worth checking out the how-to guides in the Timescale docs for full (and up to date) details.

            If no, does it have some overhead if I store my ordinary tables in PostgreSQL TimescaleDB?

            I don't think there's a storage overhead. You might see some performance gains e.g. for data ingest and query performance. This article may help clarify that https://docs.timescale.com/timescaledb/latest/overview/how-does-it-compare/timescaledb-vs-postgres/

            Overall you can think of TimescaleDB as providing additional functionality to 'vanilla' PostgreSQL and so unless there's a reason around application design to separate non-time-series data to a separate database then you aren't obliged to do that.

            One other point, shared by a very experienced member of our Slack community [thank you Chris]:

            To have time-series data and “normal” data (normalized) in one or separate databases for us came down to something like “can we asynchronously replicate the time-series information”? In our case we use two different pg systems, one replicating asynchronously (for TimescaleDB) and one with synchronous replication (for all other data).

            Transparency: I work for Timescale

            Source https://stackoverflow.com/questions/70563264


            Execute Python code with arguments inside YAML file
            Asked 2021-Dec-03 at 00:01

            I have a python code where I am passing arguments to a function using CLICK package. I have dockerized this code and using the image inside a yaml file to deploy this inside minikube on my Windows machine. It worked fine without the arguments but with argument passing, it is giving field immutable error.



            Answered 2021-Dec-03 at 00:01


            Author of the question made some changes in his Job. After the update he got a "field is immutable" error.

            This is caused by the fact that .spec.template field in Job is immutable and can not be updated.


            Delete the old Job and create a new one with necessary changes.

            Source https://stackoverflow.com/questions/70106749


            Compressed chunks: performance and data size
            Asked 2021-Nov-23 at 22:24

            I'm new to TimescaleDB and started with exploring the documentation. It's pretty clear and looks like I've missed something important.

            I've created a table:



            Answered 2021-Nov-23 at 22:24

            Typically the "time" column used to create the hypertable is not used as a segment by column while setting up compression. segment_by column is a column that has some commonality across the data set. e.g. If we have a table with device readings (device_id, event_timestamp, event_id, reading) the segment by column could be device_id (say you have a few 1000 devices and the device_readings table has data in the order of millions/billions). Note that the data in the segment by column is never stored in compressed form. Only the non segment by columns get compressed.

            Source https://stackoverflow.com/questions/70084656


            Is it possible to calculate a cumulative sum or moving average with a TimescaleDB continuous aggregate?
            Asked 2021-Nov-07 at 19:15

            Consider a table with 2 columns:



            Answered 2021-Nov-07 at 19:15

            Good question!

            You can do this by calculating a normal continuous aggregate and then doing a window function over it. So, calculate a sum() for each hour and then do sum() as a window function would work.

            When you get into more complex aggregates like average or standard deviation or percentile approximation or the like, I'd recommend switching over to some of the two-step aggregates we introduced in the TimescaleDB Toolkit. Specifically, I'd look into the statistical aggregates we recently introduced. They can also do this cumulative sum type thing. (They will only work with DOUBLE PRECISION or things that can be cast to that-ie FLOAT, I'd highly recommend you don't use NUMERIC and instead switch to doubles or floats, doesn't seem like you really need infinite precision calculations here).

            You can take a look with some queries I wrote up in this presentation but it might look something like:

            Source https://stackoverflow.com/questions/69774059


            Using time_bucket and joining multiple tables in timescaledb
            Asked 2021-Oct-28 at 20:53

            I have a simple database schema (Timescaledb) with a few tables. Each user has one main sensor with multiple metrics, each metric has its own table with user_id and timestamp.




            Answered 2021-Oct-28 at 20:53

            Yes! it's possible!

            You can try it by using regular SQL. Here is some example:

            Source https://stackoverflow.com/questions/69759949


            Does having relational tables affect the performance/scalability when using TimescaleDB?
            Asked 2021-Oct-13 at 14:30

            The chunk partitioning for hypertables is a key feature of TimescaleDB. You can also create relational tables instead of hypertables, but without the chunk partitioning.

            So if you have a database with around 5 relational tables and 1 hypertable, does it lose the performance and scalability advantage of chunk partitioning?



            Answered 2021-Oct-13 at 14:30

            One of the key advantages of TimescaleDB in comparison to other timeseries products is that timeseries data and relational data can be stored in the same database and then queried and joined together. So, "by design", it is expected that the database with several normal tables and hypertable will perform well. Usual PostgreSQL consideration about tables and other database objects, e.g., how shared memory is going to be affected, applies here.

            Source https://stackoverflow.com/questions/69542946

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install timescaledb

            TimescaleDB is available pre-packaged for several platforms:. Timescale Cloud (cloud-hosted and managed TimescaleDB) is available via free trial. You create database instances in the cloud of your choice and use TimescaleDB to power your queries, automating common operational tasks and reducing management overhead. We recommend following our detailed installation instructions.
            Linux: RedHat / CentOS Ubuntu Debian
            MacOS (Homebrew)


            Why use TimescaleDB?Migrating from PostgreSQLWriting dataQuerying and data analyticsTutorials and sample data
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries

            Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link