Re: Handling time series data with PostgreSQL

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Jayaram <jairamcbe(at)gmail(dot)com>
Cc: Adalberto Caccia <adacaccia(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Handling time series data with PostgreSQL
Date: 2020-10-07 14:41:01
Message-ID: 20201007144101.GA3063@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greetings,

* Jayaram (jairamcbe(at)gmail(dot)com) wrote:
> So, Do we need the timescaleDB as mandatory to handle time series data? Is
> there any way to handle hourly to days,months,yearly data with PGSQL alone
> without timescale addon?

Certainly there is and a lot of people do it- what isn't clear is what
it is you feel is missing from PG when it comes to handling time series
data..? Generally speaking there's concerns about PG's ability to
handle lots of partitions (which comes from there being very large
amounts of data being stored), but v12 and v13 have made great
improvements in that area and it's not nearly an issue any longer (and
performs better in quite a few cases than extensions).

> Ours is a new project and we are unsure about whether we should have both
> timescaleDB and PGSQL or PGSQL alone is capable of handling this time
> series data by tuning the right indexes.etc..

Partitioning and index tuning in PG (look at using BRIN if you haven't
already...) is important when you get to larger data volumes.

Thanks,

Stephen

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2020-10-07 14:50:07 Re: How to migrate column type from uuid to serial
Previous Message Hemil Ruparel 2020-10-07 14:40:34 Re: How to migrate column type from uuid to serial