Re: TimeScaleDB -- Open Source Time Series Database Released (www.i-programmer.info);

From: Nicolas Paris <niparisco(at)gmail(dot)com>
To: "Steve Petrie, P(dot)Eng(dot)" <apetrie(at)aspetrie(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: TimeScaleDB -- Open Source Time Series Database Released (www.i-programmer.info);
Date: 2017-04-09 11:58:42
Message-ID: 20170409115842.GB27851@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Le 09 avril 2017 à 05:31, Steve Petrie, P.Eng. écrivait :
> Warm Greetings To pgsql-general(at)postgresql(dot)org
>
> (I am a very newbie user of PG for a pretty trivial PHP / SQL web app. Been
> lurking with great admiration for a long time, on the
> pgsql-general(at)postgresql(dot)org discussion list channel.)
>
> I subscribe to a usefully wide-ranging but tightly edited source of
> tech-related news:
>
> www.i-programmer.info
>
> * * *
> * * *
>
> Here is a link to an interesting recent i-programmer article titled "Open
> Source Time Series Database Released":
>
> http://www.i-programmer.info/news/84/10648.html
>
> And here are selected snippets quoted from this i-programmer web article
> about the TimeScaleDB open source project :
>
> "A new, open-source time series database built with the Postgres engine has
> been released. TimeScaleDB is currently available in a single-node version,
> and is optimized for fast ingest and complex queries.
>
> "The developers say that it offers advantages because unlike traditional
> RDBMS, TimescaleDB it scales-out horizontally across multiple servers; while
> unlike NoSQL databases, it natively supports all of SQL
>

Thanks for the work around timeseries databases !

No mention of horizontal sharding mecanisms in the paper. Can you
provide more details ?

> ...
>
> The developers say they were unwilling to make the trade-off between the
> horizontally scalability of NoSQL and the query power of relational
> databases:
>
> "We needed something that offered both, so we built it".
> ...
>
> "The SQL support comes courtesy of the PostgreSQL engine, and includes
> features such as secondary indices, JOINs, and window functions. TimescaleDB
> acts and appears as though it is just a PostgreSQL database: You connect to
> the database as if it's PostgreSQL, and you can administer the database as
> if it's PostgreSQL. Any tools and libraries that connect with PostgreSQL
> will automatically work with TimescaleDB.
>
> "The developers say TimescaleDB offers advantages over straight PostgreSQL
> because PostgreSQL does not scale well to the volume of data that most
> time-series applications produce, especially when running on a single
> server. They say that in particular, vanilla PostgreSQL has poor write
> performance for large tables, and this problem only becomes worse over time
> as data volume grows linearly in time. These problems emerge when table
> indexes can no longer fit in memory, as each insert will translate to many
> disk fetches to swap in portions of the indexes' B-Trees.
>
> * * *
> * * *
>
> Curious to learn if any seriously PG-knowledgeable list participants have
> thoughts on this TimeScaleDB project ??
>
> Would there be merit in considering porting some TimeScaleDB functionality
> into standard Postgres, as a response to NoSQL "competition" ??
>
> Best Regards,
>
> Steve
>
> * * *
>
> Steve Petrie, P.Eng.
>
> http://aspetrie.net
> Oakville, Ontario, Canada
> (905) 847-3253
> apetrie(at)aspetrie(dot)net
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Job 2017-04-09 15:05:56 Aggregate query on large tables
Previous Message Patrick B 2017-04-09 08:31:10 Re: Nullsif ? PG 9.1